From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next 0/4] zerocopy refinements
Date: Fri, 22 Dec 2017 19:00:16 -0500 [thread overview]
Message-ID: <20171223000020.55509-1-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
1/4 is a small optimization follow-up to the earlier fix to skb_segment:
check skb state once per skb, instead of once per frag.
2/4 makes behavior more consistent between standard and zerocopy send:
set the PSH bit when hitting MAX_SKB_FRAGS. This helps GRO.
3/4 resolves a surprising inconsistency in notification:
because small packets were not stored in frags, they would not set
the copied error code over loopback. This change also optimizes
the path by removing copying and making tso_fragment cheaper.
4/4 follows-up to 3/4 by no longer allocated now unused memory.
this was actually already in RFC patches, but dropped as I pared
down the patch set during revisions.
Willem de Bruijn (4):
skbuff: in skb_segment, call zerocopy functions once per nskb
tcp: push full zerocopy packets
tcp: place all zerocopy payload in frags
tcp: do not allocate linear memory for zerocopy skbs
net/core/skbuff.c | 14 +++++++++-----
net/ipv4/tcp.c | 24 +++++++++++++++---------
2 files changed, 24 insertions(+), 14 deletions(-)
--
2.15.1.620.gb9897f4670-goog
next reply other threads:[~2017-12-23 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 0:00 Willem de Bruijn [this message]
2017-12-23 0:00 ` [PATCH net-next 1/4] skbuff: in skb_segment, call zerocopy functions once per nskb Willem de Bruijn
2017-12-23 0:00 ` [PATCH net-next 2/4] tcp: push full zerocopy packets Willem de Bruijn
2017-12-23 0:00 ` [PATCH net-next 3/4] tcp: place all zerocopy payload in frags Willem de Bruijn
2017-12-23 0:00 ` [PATCH net-next 4/4] tcp: do not allocate linear memory for zerocopy skbs Willem de Bruijn
2017-12-27 21:45 ` [PATCH net-next 0/4] zerocopy refinements David Miller
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=20171223000020.55509-1-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
/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).