From owner-freebsd-current@FreeBSD.ORG Mon Jun 7 14:11:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAB2F16A4CE for ; Mon, 7 Jun 2004 14:11:38 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 38C9143D1D for ; Mon, 7 Jun 2004 14:11:38 +0000 (GMT) (envelope-from root@pukruppa.de) Received: (qmail 32454 invoked by uid 513); 7 Jun 2004 14:14:32 -0000 Received: from root@pukruppa.de by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(213.146.114.24):SA:0(-4.9/5.0):. Processed in 0.666893 secs); 07 Jun 2004 14:14:32 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO reverse-213-146-114-24.dialin.kamp-dsl.de) (213.146.114.24) by dsl-mail.kamp.net with SMTP; 7 Jun 2004 14:14:31 -0000 Date: Mon, 7 Jun 2004 16:11:47 +0200 (CEST) From: Peter Ulrich Kruppa X-X-Sender: root@pukruppa.net To: Julian Elischer In-Reply-To: Message-ID: <20040607160206.G854@pukruppa.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: FreeBSD current users cc: net@freebsd.org Subject: Re: HEADSUP! netgraph Metadata changing. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2004 14:11:39 -0000 Hi! Sorry for topposting, but I don't know if this has got something to do with your changes: I am trying to rebuild my -CURRENT system now for some days and keep receiving panic messages from ng_ppoe like this panic NG_MKMESSAGE() with how=M_DONTWAIT(1) at line 913 in file /usr/src/sys/netgraph/ng_pppoe.c ... netgraph/pppoe is used by ppp to connect to my ISP . My last working kernel was built on May 31 . Thanks, if you know how to repair this. Uli. On Sun, 6 Jun 2004, Julian Elischer wrote: > > If you don't know or care about netgraph metadata (e.g. packet priority) > then this shouldn't worry you. > > We are changing the netgraph metadata facility (in which arbitrary > metadata can be sent with a packet through processing) to use > the mbuf TAG facility that has been imported by sam. > > Netgraph tags will use different cookies to the standard set of > tags imported with the code, so they will live in a separate namespace, > however they will be handled during GC and manipulation by the standard > tag handling code (Thanks to Sam for giving us the cookie facility). > > In the checked in code there are only a couple of users of metadata, but > there may be 3rd parties out there that use it. If so the authors should > contact me as soon as possible to co-ordinate the changeover. > > For example the BW_MAN bandwith manager uses metadata to tag > packets selected by its ipfw netgraph node. > > Currently the biggest user of metadata is the frame relay LMI > node that tags LMI packets with a higher priority in order to meet > timing constraints given by the standards. > > In addition the ng_ksocket node adds info into metadata and I suspect > there are people using that. > > > julian > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > +---------------------------+ | Peter Ulrich Kruppa | | Wuppertal | | Germany | +---------------------------+