From owner-freebsd-current@FreeBSD.ORG Fri Jan 20 10:27:12 2006 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E231B16A41F for ; Fri, 20 Jan 2006 10:27:12 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FD7043D45 for ; Fri, 20 Jan 2006 10:27:12 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 6AC1046BA3; Fri, 20 Jan 2006 05:27:08 -0500 (EST) Date: Fri, 20 Jan 2006 10:28:02 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Pyun YongHyeon In-Reply-To: <20060120051810.GB48366@rndsoft.co.kr> Message-ID: <20060120101241.O52145@fledge.watson.org> References: <20060120051810.GB48366@rndsoft.co.kr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@FreeBSD.org Subject: Re: mbuf cluster leak on CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2006 10:27:13 -0000 On Fri, 20 Jan 2006, Pyun YongHyeon wrote: > While fixing sk(4) driver issues I'm seeing these mbuf cluster leaks on > sparc64/i386. Both machines are SMP. There is at least one known problem with MBUMA's handling of allocating and freeing {mbuf,cluster} pairs, and it is triggered frequently by recent changes to cluster allocation. We need to fix this problem before 7.0, but I've been on vacation for the last month and not had a chance to dig in. I hope to address it this spring, but it requires significantly re-thinking of how UMA interacts with mbufs. Probably not a huge code change, but will have to be carefully thought out. Robert N M Watson > > sparc64(sk(4)) > 386/1946/2332 mbufs in use (current/cache/total) > 1710/290/2000/2000 mbuf clusters in use (current/cache/total/max) > ^^^^^^^^^^^^^^^^^^ > 0/5/4528 sfbufs in use (current/peak/max) > 3516K/1066K/4583K bytes allocated to network (current/cache/total) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > 0 calls to protocol drain routines > > i386(em(4)) > 388/1929/2317 mbufs in use (current/cache/total) > 1727/273/2000/2000 mbuf clusters in use (current/cache/total/max) > ^^^^^^^^^^^^^^^^^^ > 0/7/3504 sfbufs in use (current/peak/max) > 3551K/1028K/4579K bytes allocated to network (current/cache/total) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > 0 calls to protocol drain routines > > Related information from vm.zone: > mbuf_ext_ref: 4, 0, 0, 0, 0 > mbuf_jumbo_1: 16384, 0, 0, 0, 0 > mbuf_jumbo_9: 9216, 0, 0, 0, 0 > mbuf_jumbo_4: 4096, 0, 0, 0, 0 > mbuf_cluster: 2048, 2000, 2000, 0, 2000 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > mbuf: 256, 0, 788, 1657, 87811655 > mbuf_packet: 256, 0, 2160, 285, 50505646 > > To confirm the mbuf leak I lowered the cluter limit. netperf is > blocked on a "zonelimit". > Any ideas? > > -- > Regards, > Pyun YongHyeon > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >