Date: Tue, 24 Aug 2010 15:00:15 +0200 From: Andre Oppermann <andre@freebsd.org> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: pyunyh@gmail.com, freebsd-net@freebsd.org Subject: Re: 8.0-RELEASE-p3: 4k jumbo mbuf cluster exhaustion Message-ID: <4C73C25F.90903@freebsd.org> In-Reply-To: <AANLkTikBHiQ15CFKhsP4Z=9bRJEP-1_RAJAS4Y3U1GLT@mail.gmail.com> References: <AANLkTikrbCFHz-CnuYcgH2JzpeH5hob0Aa2y5dwn3Hvv@mail.gmail.com> <AANLkTikYMU=wML_z=HDnkUF1PGYMVa1q-QWTrkxD%2B7EP@mail.gmail.com> <20100822222746.GC6013@michelle.cdnetworks.com> <AANLkTi=t%2BnG8isp1nf2aBec%2BFwomApNt0NBPO8LqZ%2B=9@mail.gmail.com> <4C724AD9.5020000@freebsd.org> <AANLkTikBHiQ15CFKhsP4Z=9bRJEP-1_RAJAS4Y3U1GLT@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24.08.2010 14:37, Adrian Chadd wrote: > On 23 August 2010 18:18, Andre Oppermann<andre@freebsd.org> wrote: >> It seems the 4k clusters do not get freed back to the pool after they've >> been sent by the NIC and dropped from the socket buffer after the ACK has >> arrived. The leak must occur in one of these two places. The socket >> buffer is unlikely as it would affect not just you but everyone else too. >> Thus the mbuf freeing after DMA/tx in the bce(4) driver is the prime >> suspect. > > They don't stay leaked though. Killing the offending process sees > mbuf's eventually returned. > It isn't immediate though. It may be related to timing out existing > socket connections or something? Try "netstat -n -p tcp -x" to see whether one socket is holding on to too much data. > I haven't yet brought up the second box enough to start passing test > traffic, so I can't provide any further details than this. Testing with a different network card would help to narrow down the area to look for the bug as well. Can you describe your connection capturing setup some more? Do you use "ipfw fwd" or some form of NAT? -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C73C25F.90903>