From: Andreas Gruenbacher <agruen@linbit.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Herbert Xu <herbert@gondor.hengli.com.au>,
"David S. Miller" <davem@davemloft.net>
Subject: [RFC] [TCP 0/3] Receive from socket into bio without copying
Date: Fri, 29 Jun 2012 16:53:52 +0200 [thread overview]
Message-ID: <1340981632.25226.2.camel@gurkel.linbit> (raw)
Hello,
I'm (still) trying to pass data from the network to the block layer without
copying. The block layer needs blocks to be contiguous in memory, and may have
some alignment restrictions as well. A lot of modern network hardware will
receive large packets into separate buffers, so individual large packets will
end up in contiguous, aligned buffers. I would like to make use of that, but
tcp currently doesn't allow me to control what ends up in which packets.
This patch series introduces a new flag for indicating to tcp when it should
start a new segment. Using that on the sender side, I can get data over the
network with no cpu copying at all.
[My last posting on this topic from May 8 is archived here:
http://www.spinics.net/lists/netdev/msg197788.html ]
Thanks,
Andreas
Andreas Gruenbacher (3):
tcp: Add MSG_NEW_PACKET flag to indicate preferable packet boundaries
tcp: Zero-copy receive from a socket into a bio
fs: Export bio_release_pages()
fs/bio.c | 3 +-
include/linux/bio.h | 1 +
include/linux/socket.h | 1 +
include/net/tcp.h | 3 +
net/ipv4/Makefile | 3 +-
net/ipv4/tcp.c | 5 +-
net/ipv4/tcp_recvbio.c | 168 ++++++++++++++++++++++++++++++++++++++++++++++++
7 files changed, 180 insertions(+), 4 deletions(-)
create mode 100644 net/ipv4/tcp_recvbio.c
--
1.7.10.2
next reply other threads:[~2012-06-29 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 14:53 Andreas Gruenbacher [this message]
2012-06-29 15:08 ` [RFC] [TCP 0/3] Receive from socket into bio without copying Eric Dumazet
2012-07-02 11:45 ` Andreas Gruenbacher
2012-07-02 12:36 ` Eric Dumazet
2012-07-02 13:02 ` Andreas Gruenbacher
2012-07-02 13:54 ` Eric Dumazet
2012-07-02 16:06 ` Andreas Gruenbacher
2012-07-02 19:41 ` chetan loke
2012-07-02 21:37 ` Eric Dumazet
2012-07-03 0:02 ` Willy Tarreau
2012-07-02 13:39 ` saeed bishara
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=1340981632.25226.2.camel@gurkel.linbit \
--to=agruen@linbit.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--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