Date: Fri, 26 Oct 2001 11:06:35 +0100 From: David Malone <dwmalone@maths.tcd.ie> To: Bosko Milekic <bmilekic@technokratis.com> Cc: Luigi Rizzo <rizzo@aciri.org>, Alfred Perlstein <bright@mu.org>, net@FreeBSD.ORG Subject: Re: performance issues with M_PREPEND on clusters Message-ID: <20011026110635.B14635@walton.maths.tcd.ie> In-Reply-To: <20011023185759.A328@technokratis.com>; from bmilekic@technokratis.com on Tue, Oct 23, 2001 at 06:57:59PM -0400 References: <20011023110307.A34494@iguana.aciri.org> <20011023132813.I15052@elvis.mu.org> <20011023114650.C34494@iguana.aciri.org> <20011023140034.M15052@elvis.mu.org> <20011023140628.A36095@iguana.aciri.org> <20011023185759.A328@technokratis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 23, 2001 at 06:57:59PM -0400, Bosko Milekic wrote:
> I believe that the correct way to deal with this issue is to have
> M_LEADINGSPACE and M_TRAILINGSPACE simply return the number of bytes
> that make up the leading space or trailing space, respectively,
> regardless of whether the underlying cluster/mbuf/ext_buf is marked
> writable or not.
The only problem I can see with this tack is that we might end up
with M_LEADINGSPACE macro which does something different to the
same macro in {Net,Open}BSD. I guess we should check what their
macros do at the moment.
When I looked at this question last year I think I found that there
were few enough places in the kernel which used M_LEADINGSPACE, so
it should be fairly easy to check them. However, I think several
of the uses were in KAME code.
(I did have some notes on this work, but unfortunately the hard
drive with them on whet south recently...)
David.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011026110635.B14635>