[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA85sZu+Ptn99rsa0KrtedU8YiedOiNtULabHuvmqXEEhW0tZA@mail.gmail.com>
Date: Thu, 7 Feb 2019 11:16:51 +0100
From: Ian Kumlien <ian.kumlien@...il.com>
To: Saeed Mahameed <saeedm@....mellanox.co.il>
Cc: Cong Wang <xiyou.wangcong@...il.com>,
David Miller <davem@...emloft.net>,
Saeed Mahameed <saeedm@...lanox.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [ISSUE][4.20.6] mlx5 and checksum failures
On Thu, Feb 7, 2019 at 2:01 AM Saeed Mahameed <saeedm@....mellanox.co.il> wrote:
> On Wed, Feb 6, 2019 at 3:00 PM Ian Kumlien <ian.kumlien@...il.com> wrote:
> > It changes directly after the first hw checksum failure, I don't know why =/
>
> weird, Maybe a real check-summing issue/corruption on the PCI ?!
Actually, it seems to have been introduced in 4.20.6 - 4.20.5 works just fine
Just FYI, my dmesg testcase:
time ssh <server> "dmesg && exit
real 3m5.845s
user 0m0.035s
sys 0m0.041s
> can you try turning off checksum offloads
> ethtool -K ethX rx off
same test:
real 0m3.408s
user 0m0.022s
sys 0m0.032s
So yes, something in 4.20.6 goes wrong on the receiving part :/
Powered by blists - more mailing lists