Date: Thu, 25 Mar 1999 16:38:24 -0800 From: David Greenman <dg@root.com> To: Jonathan Lemon <jlemon@americantv.com> Cc: dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG Subject: Re: 3.1-STABLE dies on 40+ connects Message-ID: <199903260038.QAA29722@implode.root.com> In-Reply-To: Your message of "Thu, 25 Mar 1999 18:17:37 CST." <199903260017.SAA13252@free.pcs>
next in thread | previous in thread | raw e-mail | index | archive | help
>In article <local.mail.freebsd-hackers/199903252220.OAA03456@apollo.backplane.com> you write: >> netstat -tn output would be useful -- figure out what is eating so >> much memory. >> >> You should be able to raise NMBCLUSTERS to 8192 easily, and possibly >> even higher. > > >Yup. However, FBSD will still panic whne it runs out of NMBCLUSTERS. > >I have a machine with 64K mbufs, 20K NMBCLUSTERS, and if I run out of >mbuf clusters (usually because I fell behind in processing) the machine >will panic. > >Not very nice, I suppose I should go digging to fix it sometime soon. > >Can someone give a short explanation (or a pointer to the relevant code) >as to exactly when a NMBCLUSTER comes into play, instead of using a long >mbuf chain? mbufs and mbuf clusters are allocated from the same VM map (chunk of kernel virtual address space). It's the space in the VM map that is actually running out, so allocating one type of buffer over another isn't a solution. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903260038.QAA29722>