From: Anirban Chakraborty <abchak@juniper.net>
To: Wei Liu <wei.liu2@citrix.com>, annie li <annie.li@oracle.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: large packet support in netfront driver and guest network throughput
Date: Tue, 17 Sep 2013 17:53:43 +0000 [thread overview]
Message-ID: <CE5DE220.17272%abchak@juniper.net> (raw)
In-Reply-To: <20130917082526.GF22986@zion.uk.xensource.com>
On 9/17/13 1:25 AM, "Wei Liu" <wei.liu2@citrix.com> wrote:
>On Tue, Sep 17, 2013 at 10:09:21AM +0800, annie li wrote:
>><snip>
>>>>I tried dom0 to dom0 and I got 9.4 Gbps, which is what I expected
>>>>(with GRO turned on in the physical interface). However, when I run
>>>>guest to guest, things fall off. Is large packet not supported in
>>>>netfront? I thought otherwise. I looked at the code and I do not see
>>>>any call to napi_gro_receive(), rather it is using
>>>>netif_receive_skb(). netback seems to be sending GSO packets to the
>>>>netfront, but it is being segmented to 1500 byte (as it appears from
>>>>the tcpdump).
>> >>
>> >OK, I get your problem.
>> >
>> >Indeed netfront doesn't make use of GRO API at the moment.
>>
>> This is true.
>> But I am wondering why large packet is not segmented into mtu size
>> with upstream kernel? I did see large packets with upsteam kernel on
>> receive guest(test between 2 domus on same host).
>>
>
>I think Anirban's setup is different. The traffic is from a DomU on
>another host.
>
>I will need to setup testing environment with 10G link to test this.
>
>Anirban, can you share your setup, especially DomU kernel version, are
>you using upstream kernel in DomU?
Sure..
I have two hosts, say h1 and h2 running XenServer 6.1.
h1 running Centos 6.4, 64bit kernel, say guest1 and h2 running identical
guest, guest2.
iperf server is running on guest1 with iperf client connecting from guest2.
I haven't tried with upstream kernel yet. However, what I found out is
that the netback on the receiving host is transmitting GSO segments to the
guest (guest1), but the packets are segmented at the netfront interface.
Annie's setup has both the guests running on the same host, in which case
packets are looped back.
-Anirban
next prev parent reply other threads:[~2013-09-17 17:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 17:53 large packet support in netfront driver and guest network throughput Anirban Chakraborty
2013-09-13 11:44 ` Wei Liu
2013-09-13 17:09 ` Anirban Chakraborty
2013-09-16 14:21 ` Wei Liu
2013-09-17 2:09 ` annie li
2013-09-17 8:25 ` Wei Liu
2013-09-17 17:53 ` Anirban Chakraborty [this message]
2013-09-18 2:28 ` annie li
2013-09-18 21:06 ` Anirban Chakraborty
2013-09-18 15:48 ` Wei Liu
2013-09-18 20:38 ` Anirban Chakraborty
2013-09-19 9:41 ` Wei Liu
2013-09-19 16:59 ` Anirban Chakraborty
2013-09-19 18:43 ` Wei Liu
2013-09-19 19:04 ` Wei Liu
2013-09-19 20:54 ` Anirban Chakraborty
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=CE5DE220.17272%abchak@juniper.net \
--to=abchak@juniper.net \
--cc=annie.li@oracle.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 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.