From: Chris Leech <christopher.leech@intel.com>
To: lkml <linux-kernel@vger.kernel.org>, netdev <netdev@vger.kernel.org>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>
Subject: [RFC][PATCH 0/5] I/OAT DMA support and TCP acceleration
Date: Tue, 20 Dec 2005 21:17:30 -0800 [thread overview]
Message-ID: <1135142250.13781.17.camel@cleech-mobl> (raw)
Following up on the I/OAT patches that Andy posted on Nov 23, these
address some of the style concerns, add descriptive comments (kdoc
style) to many functions, remove some dead code, and most importantly
include our TCP recv offload changes.
This patch set does not include the driver for the I/OAT DMA hardware.
There are 5 patches
1) DMA subsystem
2) Networking subsystem DMA client
3) sk_buff to iovec copy helper functions
4) structure changes for TCP recv copy offload
5) main TCP recv copy offload changes
As always, comments are welcome and encouraged. I'm continuing to work
on incorporating suggestions, including the comments Deepak Saxena
posted to lkml earlier today.
The class code hasn't changed since the previous code postings, but I
think I'm making progress in figuring that out :)
I'm also looking at simplifying the DMA subsystem by removing DMA
devices in favor of only working with channels. The idea of having
devices which provide multiple channels can be managed within drivers,
without complicating the client API. That should reduce the length of
some of the dereference chains.
Chris Leech <christopher.leech@intel.com>
I/O Acceleration Technology Software Development
LAN Access Division / Digital Enterprise Group
---
drivers/Kconfig | 2
drivers/Makefile | 1
drivers/dma/Kconfig | 34 +++
drivers/dma/Makefile | 3
drivers/dma/dmaengine.c | 391 +++++++++++++++++++++++++++++++++++++++++
include/linux/dmaengine.h | 220 +++++++++++++++++++++++
include/linux/skbuff.h | 5
include/linux/tcp.h | 9
include/net/tcp.h | 10 +
net/core/Makefile | 3
net/core/dev.c | 97 ++++++++++
net/core/skbuff.c | 1
net/core/user_dma.c | 410 ++++++++++++++++++++++++++++++++++++++++++++
net/ipv4/tcp.c | 177 ++++++++++++++----
net/ipv4/tcp_input.c | 63 ++++++
net/ipv4/tcp_ipv4.c | 20 ++
net/ipv4/tcp_minisocks.c | 1
net/ipv6/tcp_ipv6.c | 1
18 files changed, 1397 insertions(+), 51 deletions(-)
reply other threads:[~2005-12-21 5:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1135142250.13781.17.camel@cleech-mobl \
--to=christopher.leech@intel.com \
--cc=andrew.grover@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).