Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751517AbWCCVkR (ORCPT ); Fri, 3 Mar 2006 16:40:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751514AbWCCVkR (ORCPT ); Fri, 3 Mar 2006 16:40:17 -0500 Received: from [198.78.49.142] ([198.78.49.142]:47620 "EHLO gitlost.site") by vger.kernel.org with ESMTP id S1751506AbWCCVkP (ORCPT ); Fri, 3 Mar 2006 16:40:15 -0500 From: Chris Leech Subject: [PATCH 0/8] Intel I/O Acceleration Technology (I/OAT) Date: Fri, 03 Mar 2006 13:40:36 -0800 To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org Message-Id: <20060303214036.11908.10499.stgit@gitlost.site> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1373 Lines: 31 This patch series is the first full release of the Intel(R) I/O Acceleration Technology (I/OAT) for Linux. It includes an in kernel API for offloading memory copies to hardware, a driver for the I/OAT DMA memcpy engine, and changes to the TCP stack to offload copies of received networking data to application space. These changes apply to DaveM's net-2.6.17 tree as of commit 2bd84a93d8bb7192ad8c23ef41008502be1cb603 ([IRDA]: TOIM3232 dongle support) They are available to pull from git://198.78.49.142/~cleech/linux-2.6 ioat-2.6.17 There are 8 patches in the series: 1) The memcpy offload APIs and class code 2) The Intel I/OAT DMA driver (ioatdma) 3) Core networking code to setup networking as a DMA memcpy client 4) Utility functions for sk_buff to iovec offloaded copy 5) Structure changes needed for TCP receive offload 6) Rename cleanup_rbuf to tcp_cleanup_rbuf 7) Add a sysctl to tune the minimum offloaded I/O size for TCP 8) The main TCP receive offload changes -- Chris Leech I/O Acceleration Technology Software Development LAN Access Division / Digital Enterprise Group - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/