[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1428571471.25985.246.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Thu, 09 Apr 2015 02:24:31 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Jan Engelhardt <jengelh@...i.de>
Cc: Linux Networking Developer Mailing List <netdev@...r.kernel.org>
Subject: Re: TSO on veth device slows transmission to a crawl
On Wed, 2015-04-08 at 19:09 +0200, Jan Engelhardt wrote:
> On Tuesday 2015-04-07 21:49, Eric Dumazet wrote:
> >> On Tuesday 2015-04-07 04:48, Eric Dumazet wrote:
> >> >On Tue, 2015-04-07 at 00:45 +0200, Jan Engelhardt wrote:
> >> >> I have here a Linux 3.19(.0) system where activated TSO on a veth slave
> [and now also 3.19.3]
> >> >> device makes IPv4-TCP transfers going into that veth-connected container
> >> >> progress slowly.
> >> >
> >> >Nothing comes to mind. It would help if you could provide a script to
> >> >reproduce the issue.
> >>
> >> It seems IPsec is *also* a requirement in the mix.
> >> Anyhow, script time!
> >
> >I tried your scripts, but the sender does not use veth ?
>
> I was finally able to reproduce it reliably, and with just one
> machine/kernel instance (and a number of containers of course).
>
> I have uploaded the script mix to
> http://inai.de/files/tso-1.tar.xz
> There is a demo screencast at
> http://inai.de/files/tso-1.mkv
Thanks for providing these scripts, but they do not work on my host
running latest net-next
Basic IP routing seems not properly enabled, as even ping does not work
to reach 10.10.23.23
ip netns exec vclient /bin/bash
ping 10.10.23.23
<no frame is sent>
Have you tried net-next as well ?
Thanks
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists