netdev - Re: HTB, HFSC, PIE, FIFO stuck on 2.4Gbit on default values

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0394a0a8c8f65e367a596274719ed759@visp.net.lb>
Date:	Wed, 04 Nov 2015 06:12:14 +0200
From:	Denys Fedoryshchenko <nuclearcat@...learcat.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	Netdev <netdev@...r.kernel.org>
Subject: Re: HTB, HFSC, PIE, FIFO stuck on 2.4Gbit on default values

On 2015-11-03 23:23, Eric Dumazet wrote:
> On Tue, 2015-11-03 at 22:24 +0200, Denys Fedoryshchenko wrote:
> 
>> I wont argue on that, you are right.
>> Ok, then it is a bit offtopic in current case, different setup, but i
>> know this one has easy to reproduce issues with offloading. but this 
>> is
>> bug related to that, directly appearing when i enable tso/gso/gro. I 
>> am
>> losing access to remote box, so max i can do right now:
>> ethtool -K eth0 tso on gso on gro on; sleep 5;ethtool -K eth0 tso off
>> gso off gro off
>> 
>> No shapers, just plain nat. I suspect it might be specific to network
>> card, but not sure.
>> 
> 
> 
> 
> What happens if you enable gro, but disable tso ?
> 
> With GRO enabled, you'll get a good performance increase, as forwarding
> and qdisc will use big packets.
Just enabling gro or gso (or together) is fine there. Thanks for advice. 
Seems only tso causing problems.
Also i guess if i keep tso disabled, it will solve my MTU issues (i had 
once issue, that traffic heading to pppoe users,
who have 14xx mtu, was blocked, when offloading enabled on transit 
server, but can't reproduce it quickly again).
Should i try to report to e1000e maintainers this bug? On similar setup 
it is happening only at specific locations,
but i am not definitely sure what can be the reason.
--
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