[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.20.1504091731410.14110@nerf40.vanv.qr>
Date: Thu, 9 Apr 2015 17:35:59 +0200 (CEST)
From: Jan Engelhardt <jengelh@...i.de>
To: Eric Dumazet <eric.dumazet@...il.com>
cc: Linux Networking Developer Mailing List <netdev@...r.kernel.org>
Subject: Re: TSO on veth device slows transmission to a crawl
On Thursday 2015-04-09 17:08, Eric Dumazet wrote:
>> >
>> >Basic IP routing seems not properly enabled, as even ping does not work
>> >to reach 10.10.23.23
>>
>> Since I have net.ipv4.conf.all.forwarding,net.ipv4.ip_forward=1
>> this probably got inherited into the containers, so I did not
>> write it down into the scripts.
>> Enable it :)
>
>The thing is : It is enabled.
If forwarding is on, and the config is reasonably correct (which
I think it is), and it still won't ping, then would that not mean
there is another bug in the kernel?
>> >Have you tried net-next as well ?
>>
>> I have now - a quick test yields no problem. Next I will do a reverse
>> bisect just for the fun.
>
>Cool ;)
I've aborted the search. v4.0-rc crashes in a VM
http://marc.info/?l=linux-kernel&m=142850643415538&w=2 , and on a
real system, the SCSI layer similarly acts up in 4.0rc5 such that sda
won't even show up in the first place. If large portions of the
history don't be booted, I can't bisect it.
--
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