Article View: comp.sys.sequent
Article #6Re: Keeping track of Fifo Buffers
From: John "Just Say Noe" Kramer
Date: Thu, 29 Oct 1992 17:16
Date: Thu, 29 Oct 1992 17:16
26 lines
1516 bytes
1516 bytes
In article <1992Oct29.070154.1695@coulomb.pcc.oz.au> parson@coulomb.pcc.oz.au (Brenda Parsons - x2403) writes: >We are currently running into problems with running out of pipes. > >I've upped the number of Fifo's allocated in the kernel from >85 to 133 and we are still hitting the limit. > >Is there any way to tell how many of the Fifo's are currently in use? >Sar doesn't seem to give any indication. > >What implications are to be had if increasing the number of fifos >available again (NFIFO = NPROC/FIFO_MULT). > >Thanks > >-brenda PTX places an upper bounds on the number of FIFO's available as these elements use the buffer cache. You may want to look at FIFOSANITY which determines the percentage of cache that may be used as FIFO space. This is case in PTX 1.4. If kernel needs to reduce this you will see a message at boot time like... "fifos reduced from 133 to 85" Ultimately the number of FIFO allowed will be limited by the size of your buffer cache.
Technical Details
Message-ID:
<1992Oct29.171617.7744@sequent.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!ukma!wupost!uwm.edu!ogicse!sequent!muncher.sequent.com!jwkReferences:
<1992Oct29.070154.1695@coulomb.pcc.oz.au>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!ukma!wupost!uwm.edu!ogicse!sequent!muncher.sequent.com!jwk From: jwk@sequent.com (John "Just Say Noe" Kramer) Newsgroups: comp.sys.sequent Subject: Re: Keeping track of Fifo Buffers Message-ID: <1992Oct29.171617.7744@sequent.com> Date: 29 Oct 92 17:16:17 GMT Article-I.D.: sequent.1992Oct29.171617.7744 References: <1992Oct29.070154.1695@coulomb.pcc.oz.au> Sender: usenet@sequent.com (usenet ) Organization: Sequent Computer Systems, Inc. Lines: 26 Nntp-Posting-Host: sequent.sequent.com