Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: James Yonan <james@openvpn.net>
Cc: Rick Jones <rick.jones2@hp.com>, netdev <netdev@vger.kernel.org>
Subject: Re: GSO/GRO and UDP performance
Date: Fri, 06 Sep 2013 12:32:35 -0700	[thread overview]
Message-ID: <1378495955.31445.52.camel@edumazet-glaptop> (raw)
In-Reply-To: <522A2C76.10203@openvpn.net>

On Fri, 2013-09-06 at 13:26 -0600, James Yonan wrote:

> Where does the 16+1 come from?  I'm getting my 43x from the ratio of max 
> legal IP packet size (64KB) / internet MTU (1500).  Are you saying that 
> GRO cannot aggregate up to 64 KB?
> 

Yes this is what I said.

Hint : MAX_SKB_FRAGS is the number of fragments per skb

Each aggregated frame consumes at least one fragment.

Hint : some drivers uses more than one fragment per datagram.

-> A fragment in skb does not necessarily contains one and exactly one
datagram

> >> I think we cannot aggregate UDP packets, because UDP lacks sequence
> >> numbers, so reorders would be a problem.
> 
> >> You really need something that is not UDP generic.
> 
> Right -- that's why I'm proposing a hook for UDP GSO/GRO providers that 
> know about specific app-layer protocols and can provide segmentation and 
> aggregation methods for them.  Such a provider would be implemented in a 
> kernel module and would know about the specific app-layer protocol, so 
> it would be able to losslessly segment and aggregate it (i.e. it could 
> use a sequence number from the app-layer protocol).

Its not a choice given by application.

As I said you'll have to make sure all the stack will understand the
meaning of datagram aggregation.

      reply	other threads:[~2013-09-06 19:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 10:07 GSO/GRO and UDP performance James Yonan
2013-09-04 11:53 ` Eric Dumazet
2013-09-06  9:22   ` James Yonan
2013-09-06 13:07     ` Eric Dumazet
2013-09-06 16:42       ` Rick Jones
2013-09-06 19:26         ` James Yonan
2013-09-06 19:32           ` Eric Dumazet [this message]

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=1378495955.31445.52.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=james@openvpn.net \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.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