Date: Mon, 30 Jan 2012 16:15:34 +0100 From: =?ISO-8859-1?Q?Ermal_Lu=E7i?= <eri@freebsd.org> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: [PATCH] multiple instances of ipfw(4) Message-ID: <CAPBZQG17C5AgBAGVHHdBDSaLGHC8Hv4waQrK165ttwVthFotbQ@mail.gmail.com> In-Reply-To: <jg69t9$6rj$1@dough.gmane.org> References: <CAPBZQG32iyzkec4PG%2Bqay9bKfd0GiffKyRBapLkATKvHr7cVww@mail.gmail.com> <jg69t9$6rj$1@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 30, 2012 at 3:36 PM, Ivan Voras <ivoras@freebsd.org> wrote: > On 30/01/2012 13:01, Ermal Lu=E7i wrote: > >> Surely i know that this is not the best way to implement generically > > > ... probably, because it's similar to VNET... > It depends on the comparison. The same argument would hold true for multiple routing tables but still they coexist. Both usages have their scopes. > >> What i would like to know is if there is interest to see such >> functionality in FreeBSD? >> >> I am asking first to see if there is some consensus about this as a >> feature, needed or not! >> If interest is shown i will transform the patch to allow: >> - ipfw(8) to manage the contextes create/destroy >> - ipfw(8) to manage interface membership. Closing the race of two >> parallell clients modifying different contextes. > > >> It is quite handy feature, which can be exploited even to scale on SMP >> machines by extending it to bind a specific instance(with its >> interaces) to a specific CPU/core?! > > > ... which is also done by VNET+JAILS. > > You should probably port it to VNET :) See above. Nevertheless, VNET is still not production use so.... > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" --=20 Ermal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPBZQG17C5AgBAGVHHdBDSaLGHC8Hv4waQrK165ttwVthFotbQ>