From owner-freebsd-net Sun Aug 27 19:43:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 6A05C37B422; Sun, 27 Aug 2000 19:43:22 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e7S2hC928224; Sun, 27 Aug 2000 19:43:12 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma028222; Sun, 27 Aug 2000 19:42:49 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id TAA66974; Sun, 27 Aug 2000 19:42:48 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008280242.TAA66974@bubba.whistle.com> Subject: Re: Proposal to clarify mbuf handling rules In-Reply-To: <20000827225011.A10714@lanczos.maths.tcd.ie> "from David Malone at Aug 27, 2000 10:50:11 pm" To: David Malone Date: Sun, 27 Aug 2000 19:42:48 -0700 (PDT) Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Malone writes: > We were thinking it might be a good idea to have a flag associated > with mbufs which means they are writable, providing the reference > count is 1. Then we can provide a macro for checking writability. > This flag could be set on jumbo ethernet buffers, but not sendfile > buffers (for example). That's a good idea.. I forgot about things like sendfile, where the mbuf is read-only due to other reasons. So we need some kind of flag it seems. That's good -- it makes it even more obvious. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message