From owner-freebsd-current Mon Nov 25 10:39:34 2002 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 6B16F37B401; Mon, 25 Nov 2002 10:39:33 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A22CA43EAA; Mon, 25 Nov 2002 10:39:32 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA06951; Mon, 25 Nov 2002 13:39:32 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gAPId2g75446; Mon, 25 Nov 2002 13:39:02 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15842.28230.205720.313119@grasshopper.cs.duke.edu> Date: Mon, 25 Nov 2002 13:39:02 -0500 (EST) To: Luigi Rizzo Cc: Robert Watson , current@freebsd.org Subject: Re: mbuf header bloat ? In-Reply-To: <20021125094815.F20370@xorpc.icir.org> References: <15840.8629.324788.887872@grasshopper.cs.duke.edu> <20021125094815.F20370@xorpc.icir.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Luigi Rizzo writes: > The mbuf bloat has two aspects -- first it does have some cost to > initialize and reset all these extra fields (and it is bug prone -- > witness is the missing cleanup in m_getcl(), because m-tags were > introduced after m_getcl() and probably it was forgotten); second, > a legitimate question might arise at some point on why some features > deserve to go there and others don't, and unfortunately the mac label > constitutes a very bad precedent because it is very large and not very > widely used (at list now) thus failing the two main important criteria > for selection what should be in and what should not. Well said. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message