Martin Pieuchot wrote: > On 02/09/15(Wed) 08:45, trondd wrote: > > I just noticed on my -current systems, memory reporting from netstat -m > > seems to show that memory is overcommited. > > > > $ netstat -m > > 535 mbufs in use: > > 289 mbufs allocated to data > > 8 mbufs allocated to packet headers > > 238 mbufs allocated to socket names and addresses > > 171/288/6144 mbuf 2048 byte clusters in use (current/peak/max) > > 0/8/6144 mbuf 4096 byte clusters in use (current/peak/max) > > 0/8/6144 mbuf 8192 byte clusters in use (current/peak/max) > > 0/14/6146 mbuf 9216 byte clusters in use (current/peak/max) > > 0/10/6150 mbuf 12288 byte clusters in use (current/peak/max) > > 0/8/6144 mbuf 16384 byte clusters in use (current/peak/max) > > 0/8/6144 mbuf 65536 byte clusters in use (current/peak/max) > > 272 Kbytes allocated to network (174% in use) <------- > > 0 requests for memory denied > > 0 requests for memory delayed > > 0 calls to protocol drain routines > > > > I see this on all -current systems, but not on 5.7-stable. I didn't see > > this on my system that was last updated to -current July 26. > > It does change the allocated Kbytes eventually but I saw it as high as 280% > > and rarely below 100%. > > This is a side effect of the *8 pool change. Diff below fixes it, ok?
ok
