From: Jason Wang <jasowang@redhat•com>
To: Wei Liu <wei.liu2@citrix•com>, netdev@vger•kernel.org
Cc: Anirban Chakraborty <abchak@juniper•net>,
Ian Campbell <ian.campbell@citrix•com>,
xen-devel@lists•xen.org
Subject: Re: [Xen-devel] [PATCH net-next] xen-netfront: convert to GRO API and advertise this feature
Date: Sun, 22 Sep 2013 14:29:15 +0800 [thread overview]
Message-ID: <523E8E3B.3050805@redhat.com> (raw)
In-Reply-To: <1379779543-27122-1-git-send-email-wei.liu2@citrix.com>
On 09/22/2013 12:05 AM, Wei Liu wrote:
> Anirban was seeing netfront received MTU size packets, which downgraded
> throughput. The following patch makes netfront use GRO API which
> improves throughput for that case.
>
> Signed-off-by: Wei Liu <wei.liu2@citrix•com>
> Signed-off-by: Anirban Chakraborty <abchak@juniper•net>
> Cc: Ian Campbell <ian.campbell@citrix•com>
Maybe a dumb question: doesn't Xen depends on the driver of host card to
do GRO and pass it to netfront? What the case that netfront can receive
a MTU size packet, for a card that does not support GRO in host? Doing
GRO twice may introduce extra overheads.
Thanks
next prev parent reply other threads:[~2013-09-22 6:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 16:05 [PATCH net-next] xen-netfront: convert to GRO API and advertise this feature Wei Liu
2013-09-22 6:29 ` Jason Wang [this message]
2013-09-22 12:09 ` [Xen-devel] " Wei Liu
2013-09-22 23:04 ` Anirban Chakraborty
2013-09-23 5:02 ` Jason Wang
2013-09-23 6:22 ` annie li
2013-09-23 20:32 ` Anirban Chakraborty
2013-09-22 14:55 ` Eric Dumazet
2013-09-22 23:09 ` Anirban Chakraborty
2013-09-23 5:58 ` Eric Dumazet
2013-09-23 20:27 ` Anirban Chakraborty
2013-09-24 16:30 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-09-28 19:38 ` David Miller
2013-09-30 9:12 ` Ian Campbell
2013-09-30 14:43 ` [Xen-devel] " Konrad Rzeszutek Wilk
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=523E8E3B.3050805@redhat.com \
--to=jasowang@redhat$(echo .)com \
--cc=abchak@juniper$(echo .)net \
--cc=ian.campbell@citrix$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=wei.liu2@citrix$(echo .)com \
--cc=xen-devel@lists$(echo .)xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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