Skip to content

zerocopy refinements

Willem de Bruijn netdev 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4skbuff: in skb_segment, call zerocopy functions once per nskbnet/core/skbuff.c+9 -50 replies
2/4tcp: push full zerocopy packetsnet/ipv4/tcp.c+3 -10 replies
3/4tcp: place all zerocopy payload in fragsnet/ipv4/tcp.c+5 -40 replies
4/4tcp: do not allocate linear memory for zerocopy skbsnet/ipv4/tcp.c+7 -40 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH net-next 0/4] zerocopy refinements

From: Willem de Bruijn <[email protected]>

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(-)
Signature · 1 line
2.15.1.620.gb9897f4670-goog