Date: Mon, 18 Nov 2013 12:23:41 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Steve Kiernan <stevek@juniper.net> Cc: FreeBSD Net <freebsd-net@freebsd.org>, Luigi Rizzo <luigi@freebsd.org>, Marcel Moolenaar <marcel@freebsd.org>, zec@freebsd.org Subject: Re: [JNPR] Network stack as a module (RFC) Message-ID: <CAJ-VmokGPUwtJ=gduRwAJ3uSZO4y1k3ZcCLKtBTiuaxxApnxPw@mail.gmail.com> In-Reply-To: <20131118142026.500fcba5@stevek-ubuntu> References: <CC6EF6B2.1917A%anshukla@juniper.net> <f1d8693fa83965f0d4a485a2db7e603b@novexsolutions.com> <50F868FF.5060506@networx.ch> <20131115165210.23f82578@stevek-ubuntu> <CAJ-Vmo=gd-bwLxw2LTXEJwY=4mJWxQS-HwGC_gbw-VtSfLBTCg@mail.gmail.com> <20131118142026.500fcba5@stevek-ubuntu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18 November 2013 11:20, Steve Kiernan <stevek@juniper.net> wrote: > > Sure, that's fine with me. I had been considering back and forth about > whether or not to add NETSTACK to the NIC drivers and the like. > I went with adding it in for completeness sake, but I'm good with not > having to add it for drivers. ok. let's do that. So ideally (!), the aim is to make it so it's both selectable as buildable _and_ loadable as a module, right? The drivers will ideally treat the if/ifnet stuff as opaque as possible and use methods/macros to access things. (if they use methods, then we can turn some of them into macros for source builds, but have an option to turn them into actual methods that can be indirected easily enough for what you need.) How's that sound? -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokGPUwtJ=gduRwAJ3uSZO4y1k3ZcCLKtBTiuaxxApnxPw>