From: Daniel Lezcano <dlezcano@fr.ibm.com>
To: Ryousei Takano <ryousei@gmail.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Linux Containers <containers@lists.osdl.org>,
Linux Netdev List <netdev@vger.kernel.org>,
lxc-devel@lists.sourceforge.net
Subject: Re: [lxc-devel] Poor bridging performance on 10 GbE
Date: Thu, 19 Mar 2009 10:08:00 +0100 [thread overview]
Message-ID: <49C20B70.7050509@fr.ibm.com> (raw)
In-Reply-To: <b30d1c3b0903182237w7667c5bbt1ea098025f3b5f36@mail.gmail.com>
Ryousei Takano wrote:
> Hi Eric,
>
> On Thu, Mar 19, 2009 at 9:50 AM, Eric W. Biederman
> <ebiederm@xmission.com> wrote:
>
> [snip]
>
>> Bridging last I looked uses the least common denominator of hardware
>> offloads. Which likely explains why adding a veth decreased your
>> bridging performance.
>>
> At least now LRO cannot coexist bridging.
> So I disable the LRO feature of the myri10ge driver.
>
>>>>> Here is my experimental setting:
>>>>> OS: Ubuntu server 8.10 amd64
>>>>> Kernel: 2.6.27-rc8 (checkout from the lxc git repository)
>>>> I would recommend to use the 2.6.29-rc8 vanilla because this kernel does no
>>>> longer need patches, a lot of fixes were done in the network namespace and
>>>> maybe the bridge has been improved in the meantime :)
>>>>
>>> I checked out the 2.6.29-rc8 vanilla kernel.
>>> The performance after issuing lxc-start improved to 8.7 Gbps!
>>> It's a big improvement, while some performance loss remains.
>>> Can not we avoid this loss?
>> Good question. Any chance you can profile this and see where the
>> performance loss seems to be coming from?
>>
> I found out this issue is caused by decreasing the MTU size.
> Myri-10G's MTU size is 9000 bytes; the veth' MTU size is 1500 bytes.
> After bridging veth, MTU size decreases from 9000 to 1500 bytes.
> I changed the veth's MTU size to 9000 bytes, and then I confirmed
> the throughput improved to 9.6 Gbps.
>
> The throughput between LXC containers also improved to 4.9 Gbps
> by changing the MTU sizes.
>
> So I propose to add lxc.network.mtu into the LXC configuration.
> How does that sound?
Sounds good :)
Do you plan to send a patch ?
next prev parent reply other threads:[~2009-03-19 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b30d1c3b0903180221h5175618eue162ffdec3817b4c@mail.gmail.com>
2009-03-18 10:10 ` [lxc-devel] Poor bridging performance on 10 GbE Daniel Lezcano
2009-03-18 15:56 ` Ryousei Takano
2009-03-19 0:50 ` Eric W. Biederman
2009-03-19 5:37 ` Ryousei Takano
2009-03-19 9:08 ` Daniel Lezcano [this message]
2009-03-19 10:50 ` Ryousei Takano
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=49C20B70.7050509@fr.ibm.com \
--to=dlezcano@fr.ibm.com \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=lxc-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=ryousei@gmail.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;
as well as URLs for NNTP newsgroup(s).