Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: Emmanuel Jeanvoine <emmanuel.jeanvoine@inria.fr>, netdev@vger.kernel.org
Subject: Re: Poor TCP bandwidth between network namespaces
Date: Fri, 08 Feb 2013 18:17:10 -0800	[thread overview]
Message-ID: <1360376230.6696.7.camel@edumazet-glaptop> (raw)
In-Reply-To: <1360373618.6696.2.camel@edumazet-glaptop>

On Fri, 2013-02-08 at 17:33 -0800, Eric Dumazet wrote:

> Another thing to consider is the default MTU value :
> 
> 65536 for lo, and 1500 for veth
> 
> It easily explains half performance for veth
> 
> One another thing is the tx-nocache-copy setting, this can explain some
> extra percents.

By the way I get crashes when doing :

# ip link add name veth1 type veth peer name veth0
# rmmod veth

I'll submit a patch.

      parent reply	other threads:[~2013-02-09  2:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 14:43 Poor TCP bandwidth between network namespaces Emmanuel Jeanvoine
2013-02-04 22:52 ` Hannes Frederic Sowa
2013-02-09  1:33   ` Eric Dumazet
2013-02-09  1:54     ` Rick Jones
2013-02-09  2:17     ` 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=1360376230.6696.7.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=emmanuel.jeanvoine@inria.fr \
    --cc=hannes@stressinduktion.org \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox