Date: Tue, 26 Nov 2002 19:15:26 -0500 From: Bosko Milekic <bmilekic@unixdaemons.com> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: current@freebsd.org Subject: Re: mbuf header bloat ? Message-ID: <20021126191526.B78371@unixdaemons.com> In-Reply-To: <15842.51914.871010.137070@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Mon, Nov 25, 2002 at 08:13:46PM -0500 References: <15840.8629.324788.887872@grasshopper.cs.duke.edu> <Pine.BSF.4.21.0211232306410.28833-100000@InterJet.elischer.org> <15841.17237.826666.653505@grasshopper.cs.duke.edu> <20021125130005.A75177@unixdaemons.com> <15842.27547.385354.151541@grasshopper.cs.duke.edu> <20021125160122.A75673@unixdaemons.com> <15842.51914.871010.137070@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 25, 2002 at 08:13:46PM -0500, Andrew Gallatin wrote: > > It is not out of date. The code means: > > > > "If you've given me a counter then I'll use it otherwise I'll try to > > allocate one with malloc()." > > Ah, duh. Thanks. I'd better start providing one in my driver then.. Again, if you're just using regular mbuf clusters (of the 2K variety) you don't need to because mb_alloc will do it for you. If you're using a third-party buffer (e.g., jumbo buf) then you can if you want to but make sure it's not something that requires freeing afterwords (in other words, only do it if you do the exact same thing mb_alloc does for regular clusters because otherwise you'll have to worry about destructing the counter before freeing the mbuf). > Drew -- Bosko Milekic * bmilekic@unixdaemons.com * bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021126191526.B78371>