From owner-freebsd-current Fri Feb 12 16:16:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29293 for freebsd-current-outgoing; Fri, 12 Feb 1999 16:16:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29285; Fri, 12 Feb 1999 16:16:15 -0800 (PST) (envelope-from ccsanady@friley-185-205.res.iastate.edu) Received: from friley-185-205.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id 93D2E10; Fri, 12 Feb 1999 18:16:13 -0600 (CST) X-Mailer: exmh version 2.0.2 2/24/98 To: Jason Thorpe Cc: justin@apple.com, freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Serious mbuf cluster leak.. In-reply-to: Your message of "Fri, 12 Feb 1999 12:53:18 PST." <199902122053.MAA04612@lestat.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Feb 1999 18:16:13 -0600 From: Chris Csanady Message-Id: <19990213001613.93D2E10@friley-185-205.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Thu, 11 Feb 1999 09:15:29 -0800 > "Justin C. Walker" wrote: > > > I can say that our implementation doesn't seem to = > > suffer from this problem. Could be there's an issue in the use of = > > PRUS_* v. the socket state we use. The code in my kernel looks like: > >The NetBSD code looks pretty much just like this, and also does not >suffer from an mbuf cluster leak of any kind. I'll take a look at the NetBSD code when I have a chance. Are you sure you just have not seen it though? I only see it over gigabit ethernet, and even then only when doing lots of large writes. Perhaps it is a timing issue? I am only pointing out what I see. It does not happen with source from before this change--so what else should I think? You are welcome to take a glance at my driver, although I don't think it is the problem. There are only 2 places where clusters are touched, and they never become seperate from the mbuf header. But I don't see any mbuf leak.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message