From owner-freebsd-current@FreeBSD.ORG Fri Nov 16 00:13:30 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE10216A41A for ; Fri, 16 Nov 2007 00:13:30 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 3B0E713C448 for ; Fri, 16 Nov 2007 00:13:29 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 66950 invoked from network); 15 Nov 2007 23:47:42 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 15 Nov 2007 23:47:42 -0000 Message-ID: <473CE0B2.5000703@freebsd.org> Date: Fri, 16 Nov 2007 01:13:38 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.13 (Windows/20070809) MIME-Version: 1.0 To: Jack Vogel References: <1B860D81B4F3F44398B9AE84D91C151671D11B@stlex510.dsto.defence.gov.au> <2a41acea0711141712x533bcdbex92df05280311be8e@mail.gmail.com> <473BA656.7020508@elischer.org> <2a41acea0711150058v5eaa2866v40eb0c0bc65b4ede@mail.gmail.com> In-Reply-To: <2a41acea0711150058v5eaa2866v40eb0c0bc65b4ede@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org, Julian Elischer , "Wilkinson, Alex" Subject: Re: I/OAT ... Coming Soon ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2007 00:13:30 -0000 Jack Vogel wrote: > On Nov 14, 2007 5:52 PM, Julian Elischer wrote: >> Jack Vogel wrote: >>> On Nov 14, 2007 5:01 PM, Wilkinson, Alex >>> 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