From: Eric Dumazet <erdnetdev@gmail.com>
To: Andrew Vagin <avagin@parallels.com>
Cc: netdev@vger.kernel.org, vvs@parallels.com,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Subject: Re: Slow speed of tcp connections in a network namespace
Date: Sat, 29 Dec 2012 09:40:28 -0800 [thread overview]
Message-ID: <1356802828.21409.4623.camel@edumazet-glaptop> (raw)
In-Reply-To: <20121229145030.GA7959@paralelels.com>
On Sat, 2012-12-29 at 18:50 +0400, Andrew Vagin wrote:
> On Sat, Dec 29, 2012 at 05:53:23AM -0800, Eric Dumazet wrote:
> > > 3.8-rc1 is used for experiments.
> > >
> > > Do you have any ideas where is a problem?
> >
> > veth has absolutely no offload features
> >
> > It needs some care...
> >
> > At the very miminum, let TCP coalesce do its job by allowing SG
> >
> > CC Michał Mirosław <mirq-linux@rere.qmqm.pl> for insights.
> >
> > Please try following patch :
>
> Hello Eric,
>
> Thanks for your feedback.
>
> With this patch the results is a bit better (~4MB/s), but it's much less
> than in the root netns.
Please post your new tcpdump then ;)
also post "netstat -s" from root and test ns after your wgets
next prev parent reply other threads:[~2012-12-29 17:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 9:24 Slow speed of tcp connections in a network namespace Andrew Vagin
2012-12-29 13:53 ` Eric Dumazet
2012-12-29 14:50 ` Andrew Vagin
2012-12-29 17:40 ` Eric Dumazet [this message]
2012-12-29 18:29 ` Andrew Vagin
2012-12-29 18:58 ` Eric Dumazet
2012-12-29 19:41 ` Eric Dumazet
2012-12-29 20:08 ` Andrew Vagin
2012-12-29 20:20 ` Eric Dumazet
2012-12-29 21:07 ` Andrew Vagin
2012-12-29 21:12 ` Eric Dumazet
2012-12-29 21:19 ` Andrew Vagin
2012-12-29 21:15 ` Andrew Vagin
2012-12-29 16:01 ` Michał Mirosław
2012-12-30 2:26 ` [PATCH] veth: extend device features Eric Dumazet
2012-12-30 10:32 ` 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=1356802828.21409.4623.camel@edumazet-glaptop \
--to=erdnetdev@gmail.com \
--cc=avagin@parallels.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.kernel.org \
--cc=vvs@parallels.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