Date: Wed, 13 Aug 2003 19:47:01 -0400 From: "Matthew Emmerton" <matt@compar.com> To: "Craig Rodrigues" <rodrigc@crodrigues.org>, <freebsd-current@freebsd.org> Subject: Re: M_NOTIFICATION in <sys/mbuf.h>? Message-ID: <003901c361f5$317db6b0$1200a8c0@gsicomp.on.ca> References: <20030913233905.GA3834@crodrigues.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi, > > While trying to port the SCTP-KAME code to CURRENT, > I noticed that M_NOTIFICATION is missing from <sys/mbuf.h> > in CURRENT, but it is present in the KAME version of this > file. > > Any reason not to apply this patch? > > --- sys/sys/mbuf.h.orig Sat Sep 13 19:34:07 2003 > +++ sys/sys/mbuf.h Sat Sep 13 19:34:14 2003 > @@ -164,6 +164,8 @@ > #define M_FIRSTFRAG 0x1000 /* packet is first fragment */ > #define M_LASTFRAG 0x2000 /* packet is last fragment */ > > +#define M_NOTIFICATION 0x8000 /* notification event */ > + > /* > * External buffer types: identify ext_buf type. > */ > > KAME guys have it here: > http://orange.kame.net/dev/cvsweb.cgi/kame/freebsd5/sys/sys/mbuf.h?rev=1.5 The KAME snapshot of our source tree is 3 months out of date. The most recent version of mbuf.h is here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/sys/mbuf.h?rev=1.122&content-type=text/plain We already have 0x8000 assigned, and the only free flags value is 0x4000 -- but it conflicts with other private usages in the kernel (as per the CVS comments.) Does SCTP-KAME really need a special flag value? -- Matt Emmerton
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003901c361f5$317db6b0$1200a8c0>