From owner-freebsd-arch@FreeBSD.ORG Tue Aug 31 20:51:03 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 698A416A4CE; Tue, 31 Aug 2004 20:51:03 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AE2E43D46; Tue, 31 Aug 2004 20:51:03 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id B836C7A3F9; Tue, 31 Aug 2004 13:51:02 -0700 (PDT) Message-ID: <4134E4B6.2030409@elischer.org> Date: Tue, 31 Aug 2004 13:51:02 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Brooks Davis References: <4134DF35.7070605@freebsd.org> <20040831203929.GB25134@odin.ac.hmc.edu> In-Reply-To: <20040831203929.GB25134@odin.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Sam cc: Scott Long cc: freebsd-arch@freebsd.org Subject: Re: option directive and turning on AOE X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2004 20:51:03 -0000 Brooks Davis wrote: >On Tue, Aug 31, 2004 at 02:27:33PM -0600, Scott Long wrote: > > >>Sam wrote: >> >> >> >>>I've added code to if_ethersubr.c:/ether_demux/ >>>to queue up AoE frames as they appear. I followed >>>suit with other protocols and included my addition >>>inside of an #ifdef AOE. Where do I turn this on? >>>I thought perhaps just adding an 'option AOE' to >>>the config would do it, but it doesn't -- so clearly >>>I don't understand how the option directive works. >>>The config man page doesn't talk about option/device >>>directives ... >>> >>>I'm still looking, but a clue would be well received. >>> >>> >>Did you modify /sys/conf/options to tell it about your >>AOE option? If so, then you should have specified the name >>of a header file that the option would be #define'd into. >>Include that header file in if_ethersubr.c and you should >>have no problems. >> >>Incidentally, this might be an area when netgraph would be >>useful. Instead of having an AoE specific hook in the >>stack, you could have an AoE netgraph module that uses the >>existing netgraph hooks. It's just an idea, though. >> >> > >Another option might be a PFIL hook. There isn't one there now, but I >think I've seen talk of adding one. Actually, if we did that, we could >get most of the netgraph specific hooks out of the ethernet code. > or visa versa.. make pfil have a netgraph hook. then you could use it to filter all kinds of things in netgraph graphs. :-) > >-- Brooks > > >