From owner-freebsd-current  Fri Feb 12 12:53:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA04972
          for freebsd-current-outgoing; Fri, 12 Feb 1999 12:53:36 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04956;
          Fri, 12 Feb 1999 12:53:34 -0800 (PST)
          (envelope-from thorpej@lestat.nas.nasa.gov)
Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id MAA04612; Fri, 12 Feb 1999 12:53:19 -0800 (PST)
Message-Id: <199902122053.MAA04612@lestat.nas.nasa.gov>
To: justin@apple.com
Cc: Chris Csanady <ccsanady@friley-185-205.res.iastate.edu>,
        freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG
Subject: Re: Serious mbuf cluster leak.. 
Reply-To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Jason Thorpe <thorpej@nas.nasa.gov>
Date: Fri, 12 Feb 1999 12:53:18 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 11 Feb 1999 09:15:29 -0800 
 "Justin C. Walker" <justin@apple.com> 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.

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message