Date: Mon, 18 Nov 2013 20:41:49 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: luigi@freebsd.org, Marcel Moolenaar <marcel@freebsd.org>, Steve Kiernan <stevek@juniper.net>, freebsd-net@freebsd.org, zec@freebsd.org Subject: Re: [JNPR] Network stack as a module (RFC) Message-ID: <20131118164149.GV7577@glebius.int.ru> In-Reply-To: <1DAF9090-08DA-404B-B86B-57E5D124D70D@xcllnt.net> References: <CC6EF6B2.1917A%anshukla@juniper.net> <f1d8693fa83965f0d4a485a2db7e603b@novexsolutions.com> <50F868FF.5060506@networx.ch> <20131115165210.23f82578@stevek-ubuntu> <20131116084919.GF7577@glebius.int.ru> <1DAF9090-08DA-404B-B86B-57E5D124D70D@xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcel, On Sun, Nov 17, 2013 at 10:10:15AM -0800, Marcel Moolenaar wrote: M> > S> Add a NETSTACK option to facilitate separating network stack pieces from the M> > S> rest of the OS core. This is the first step towards having the network stack M> > S> as a module. M> > M> > You probably mean "having the network stack optional", since under module we M> > usually mean loadable kernel module. M> M> Actually, we do mean module. At Juniper we have the FreeBSD stack M> as a loadable module now. We also have the Juniper stack as a M> loadable module. Depending on context, we can use the most M> appropriate one. Yes, this implies that we also have a stable M> interface between the NIC driver and the network stack itself. M> We'll be contributing that as well... M> M> Note that assumptions in the finalization of setting up networking M> limits the network stack from being loaded manually, not to mention M> that unloading is an entirely different challenge. Nonetheless it's M> very useful without all that and I think it will make it easier for M> people to change the network stack or experiment with beta versions M> this way. Have you measured the performance impact on the loadable stack? I suppose many functions, that are now called directly, with loadable stack will be called via functon pointers. M> It all really comes in handy for the opaque ifnet work... Actually I wanted to start it for a long time. But since at EuroBSDCon 2011 you said that you plan to import Junipers' transform of ifnet, I held off my intentions. Until now I was almost sure that plan on brining junipers ifnet was abandoned. -- Totus tuus, Glebius.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131118164149.GV7577>