Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!emory!hubcap!ncrcae!sauron!nncrcae!wescott
From: wescott@Columbia.NCR.COM (Mike Wescott)
Newsgroups: comp.sys.ncr
Subject: Re: 32-600 HPSIO HELP?!?!?!: what is "threshold on overrun tally error"
Message-ID: <1990Oct17.151218.24071@nncrcae.Columbia.NCR.COM>
Date: 17 Oct 90 15:12:18 GMT
References: <1990Oct11.165115.4811@holos0.uucp> <1990Oct12.184451.2985@nncrcae.Columbia.NCR.COM> <496@texbell.sbc.com>
Sender: usenet@nncrcae.Columbia.NCR.COM
Organization: E&M-Columbia, NCR Corp, W Columbia, SC
Lines: 14

In article <496@texbell.sbc.com> root@texbell.sbc.com (Greg Hackney) writes:
> In article <1990Oct12.184451.2985@nncrcae.Columbia.NCR.COM> wescott@Columbia.NCR.COM (Mike Wescott) writes:
>>It means that some number (the threshold) of overrun events (hpsio
>>not getting characters out of uart before they're clobbered by more
>>characters arriving) have occurred.

> Mike, is this affected by the number of NCLISTs in the kernel configuration?

Nope.  The hpsio will also invoke flow control when the low water mark is
reached but the "overrun" error is an indication that interrupts weren't
serviced quickly enough.
--
	-Mike Wescott
	 mike.wescott@ncrcae.Columbia.NCR.COM