Date: Fri, 16 Nov 2007 01:13:38 +0100 From: Andre Oppermann <andre@freebsd.org> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org, Julian Elischer <julian@elischer.org>, "Wilkinson, Alex" <Alex.Wilkinson@dsto.defence.gov.au> Subject: Re: I/OAT ... Coming Soon ? Message-ID: <473CE0B2.5000703@freebsd.org> In-Reply-To: <2a41acea0711150058v5eaa2866v40eb0c0bc65b4ede@mail.gmail.com> References: <1B860D81B4F3F44398B9AE84D91C151671D11B@stlex510.dsto.defence.gov.au> <2a41acea0711141712x533bcdbex92df05280311be8e@mail.gmail.com> <473BA656.7020508@elischer.org> <2a41acea0711150058v5eaa2866v40eb0c0bc65b4ede@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jack Vogel wrote: > On Nov 14, 2007 5:52 PM, Julian Elischer <julian@elischer.org> wrote: >> Jack Vogel wrote: >>> On Nov 14, 2007 5:01 PM, Wilkinson, Alex >>> <Alex.Wilkinson@dsto.defence.gov.au> wrote: >>>> Hi all, >>>> >>>> Curious, is I/OAT [http://www.intel.com/go/ioat/] coming to FreeBSD soon >>>> ? >>> LOL, I did a driver for the first version of I/OAT more than a year >>> ago, submitted >>> it and interest was half hearted. >>> >>> The driver needs updating and polishing yet, but interest being what it was >>> it hasn't been a real high priority. >>> >> I saw what I thought you called a "preliminary" driver. >> There was discussion and I thought you got positive but >> muted (along the lines of "nice.. when will there be hardware for it?") >> and some discussion of how it fits in with TCP offload, but I don't think >> that anyone said they didn't like the idea.. >> >> hmm didn't someone else have an implementation? or am I getting >> my wires crossed on that? > > You are probably right, its been quite a while, and there were > other factors that have effected my perception. > > The driver just for the engine didn't require the stack portion > that Prafulla did, although we need something using the thing :) I/OAT helps with the userland/kernel copying by offloading it into the chipset memory controller. The right place to hook it isn't really the network stack but copyin/copyout and equivalents. m_uiotombuf and uiomove in this case for sockets. > Not sure what other implementation you are thinking of. Linux has it > of course. > > I'd be glad to resurrect the code and get on with it in any case. -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?473CE0B2.5000703>