Date: Wed, 11 May 2016 11:27:20 -0700 From: "K. Macy" <kmacy@freebsd.org> To: Chris H <bsd-lists@bsdforge.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Questions on iflib Message-ID: <CAHM0Q_PrdE3mJCFhL9aDJxY_y0bnmPEfPx8WL%2BO24ADpbg4sZQ@mail.gmail.com> In-Reply-To: <8cf1894ea5271efab3f544e378679cb2@ultimatedns.net> References: <DM2PR11MB0222EA7D872EA508FC1E45A9F4710@DM2PR11MB0222.namprd11.prod.outlook.com> <20160510172524.GK79033@strugglingcoder.info> <8cf1894ea5271efab3f544e378679cb2@ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 11, 2016 at 7:56 AM, Chris H <bsd-lists@bsdforge.com> wrote: > On Tue, 10 May 2016 10:25:24 -0700 hiren panchasara > <hiren@strugglingcoder.info> wrote > >> + Kip, Scott. >> >> On 05/10/16 at 04:46P, David Somayajulu wrote: >> > Hi All, >> > I have a couple of questions on iflib : >> > >> > 1. Are there plans to incorporate iflib into CURRENT. If yes, will it >> > make it into FreeBSD11 release ? >> >> Yes. The library itself (without any drivers) is being prepared for >> committing to CURRENT. > This is intended to be optional. Right? The name Iflib is short for iflnet library. A driver has to be programmed to it. It will always be possible to program directly to ifnet, but henceforth it will be frowned upon when not absolutely necessary. As iflib will ultimately make the driver more performant and more maintainable. As a counterexample, the Chelsio driver has to manage multiple ports on a single device and handle synchronization with upper level protocols. It's also extremely well optimized already. I don't know of any other network driver that can justify opting out for one of those reasons, much less both. -M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHM0Q_PrdE3mJCFhL9aDJxY_y0bnmPEfPx8WL%2BO24ADpbg4sZQ>