Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Jan 2003 16:17:42 -0500 (EST)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        Bosko Milekic <bmilekic@unixdaemons.com>
Cc:        current@freebsd.org
Subject:   Re: mbuf header bloat ?
Message-ID:  <15892.44150.747656.722752@grasshopper.cs.duke.edu>
In-Reply-To: <20030102160028.A25488@unixdaemons.com>
References:  <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> <20021126191526.B78371@unixdaemons.com> <15892.35521.181516.714686@grasshopper.cs.duke.edu> <20030102152930.A25321@unixdaemons.com> <15892.42354.150878.922603@grasshopper.cs.duke.edu> <20030102160028.A25488@unixdaemons.com>

next in thread | previous in thread | raw e-mail | index | archive | help

Bosko Milekic writes:
 > 
 >   Yeah, this looks like the least-intrusive way to do it.  I'm okay with
 >   the patch.  I like the idea of using an EXT-type flag to mark the data
 >   buffer types using this method.  Thanks.

Thanks.. Committed.

 >   P.S.: Try not to use MEXTADD, if possible.  Use m_extadd() instead,
 >   which is the procedure-equivalent version.  MEXTADD is just provided
 >   for 'backwards-compatibility'.  It used to be a large ugly macro.

Oh, OK.  That's fine.  I'm happy to just use m_extadd().  Thanks for
the tip.

Drew

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?15892.44150.747656.722752>