From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next-2.6] gro: drivers should feed GRO only with TCP packets
Date: Wed, 01 Sep 2010 10:48:05 -0700 (PDT) [thread overview]
Message-ID: <20100901.104805.35816252.davem@davemloft.net> (raw)
In-Reply-To: <20100901104235.5476a242@nehalam>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Wed, 1 Sep 2010 10:42:35 -0700
> There was talk of doing GRO for UDP as well but it never
> got implemented.
I suppose the most direct application would be for IP fragmentation.
In fact I could see that working very well.
But for non-fragmented UDP... I can't see much value to that.
We'd have to preserve the packet boundaries, and process each chunk of
data as one packet at a time within those boundaries, to retain
datagram recvmsg() semantics.
next prev parent reply other threads:[~2010-09-01 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 17:04 [RFC PATCH net-next-2.6] gro: drivers should feed GRO only with TCP packets Eric Dumazet
2010-09-01 17:42 ` Stephen Hemminger
2010-09-01 17:48 ` David Miller [this message]
2010-09-01 17:55 ` Stephen Hemminger
2010-09-01 20:10 ` 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=20100901.104805.35816252.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.