netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH v2 net-next] net: gro: remove obsolete code from skb_gro_receive()
Date: Fri, 06 Mar 2015 01:04:41 -0500 (EST)	[thread overview]
Message-ID: <20150306.010441.1755035570297062470.davem@davemloft.net> (raw)
In-Reply-To: <1425592068.5130.266.camel@edumazet-glaptop2.roam.corp.google.com>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 05 Mar 2015 13:47:48 -0800

> From: Eric Dumazet <edumazet@google.com>
> 
> Some drivers use copybreak to copy tiny frames into smaller skb,
> and this smaller skb might not have skb->head_frag set for various
> reasons.
> 
> skb_gro_receive() currently doesn't allow to aggregate the smaller skb
> into the previous GRO packet if this GRO packet has at least 2 MSS in
> it.
> 
> Following workload easily demonstrates the problem.
> 
> netperf -t TCP_RR -H target -- -r 3000,3000 
> 
> (tcpdump shows one GRO packet with 2 MSS, plus one additional packet of
> 104 bytes that should have been appended.)
> 
> It turns out that we can remove code from skb_gro_receive(), because
> commit 8a29111c7ca6 ("net: gro: allow to build full sized skb") and its
> followups removed the assumption that a GRO packet with a frag_list had
> to have an empty head.
> 
> Removing this code allows the aggregation of the last (incomplete) frame
> in some RPC workloads. Note that tcp_gro_receive() already takes care of
> forcing a flush if necessary, including this case.
> 
> If we want to avoid using frag_list in the first place (in forwarding
> workloads for example, as the outgoing NIC is generally not able to cope
> with skbs having a frag_list), we need to address this separately.
> 
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> ---
> v2: removed headroom & nskb variables, no longer needed.

Looks good, applied, thanks!

  reply	other threads:[~2015-03-06  6:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 18:26 [PATCH net-next] net: gro: remove obsolete code from skb_gro_receive() Eric Dumazet
2015-03-05 21:00 ` David Miller
2015-03-05 21:04   ` Eric Dumazet
2015-03-05 21:47 ` [PATCH v2 " Eric Dumazet
2015-03-06  6:04   ` David Miller [this message]
2015-03-06 20:39     ` Eric Dumazet
2015-03-06 20:59       ` David Miller
2015-03-06 23:56         ` Eric Dumazet
2015-03-07  3:02           ` 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=20150306.010441.1755035570297062470.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --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).