network buffer allocs failing in 2.1.57: normal?
kwrohrer@enteract.com
Wed, 15 Oct 1997 12:01:36 -0500 (CDT)
And lo, Rogier Wolff saith unto me:
> ADAM Sulmicki wrote:
> > ->> Oct 14 17:15:38 eax kernel: Networking buffers in use : 172504
> > ->So right now you have 172,504 network buffers - thats at least 17Mbytes
> > ->of them. I guess thats what is leaking. Now does 2.0.29 leak on the same
> > ->configuration ?
> >
> > That's bit little, my estimates are that I'm missing at least 40-60mb of
> > ram [hard to say w/out going into single user mode]
>
> Oct 15 11:20:38 cave kernel: Networking buffers in use : 2
> Oct 15 11:20:38 cave kernel: Network buffers locked by drivers : 0
> Oct 15 11:20:38 cave kernel: Total network buffer allocations : 74700
> Oct 15 11:20:38 cave kernel: Total failed network buffer allocs : 0
> Oct 15 11:20:38 cave kernel: Total free while locked events : 0
> Oct 15 11:20:38 cave kernel: IP fragment buffer size : 0
> Oct 15 11:20:39 cave kernel:
>
> This is "normal" for a networked machine. Just a few buffers in use.
Meanwhile, with 2.1.57 I see many failed network buffer allocations
(~7% of the total network buffer allocations), and no printout line
for locked buffers. Side question: are lots of failed buffer allocations
the norm for 2.1 kernels? I have 32M of RAM, an NE2000, and do NFS;
I do get various network-out-of-memory bits and occasional long pauses
in NFS service (sometimes to the point of repeated timeout errors
hitting the log)... The server has 24M of RAM, and also runs 2.1.57
(and the user-space nfsd)...
Keith