[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALzJLG8h7oYPQrU5RK1j7zaNA0wvFOET55WvjMjZaoQqkmiDBQ@mail.gmail.com>
Date: Mon, 16 Jan 2017 22:15:51 +0200
From: Saeed Mahameed <saeedm@....mellanox.co.il>
To: Tom Herbert <tom@...bertland.com>
Cc: Leon Romanovsky <leon@...nel.org>,
David Miller <davem@...emloft.net>,
Saeed Mahameed <saeedm@...lanox.com>,
Doug Ledford <dledford@...hat.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
linux-rdma@...r.kernel.org
Subject: Re: [pull request][for-next] Mellanox mlx5 Reorganize core driver
directory layout
On Sat, Jan 14, 2017 at 12:56 AM, Tom Herbert <tom@...bertland.com> wrote:
> On Fri, Jan 13, 2017 at 2:45 PM, Saeed Mahameed
> <saeedm@....mellanox.co.il> wrote:
>> On Sat, Jan 14, 2017 at 12:06 AM, Tom Herbert <tom@...bertland.com> wrote:
>>> Btw, we did hit one issue in the backport. We started to get rx csum
>>> faults (checksum complete value indicates TCP checksum is bad, but
>>> host computation says checksum is good). I ran against 4.9 upstream
>>> kernel and do see these, however don't see them in 4.10. I haven't
>>> bisected yet. Is this a known issue?
>>>
>>
>> Not to me, I don't recall any csum related fixes or feature submitted
>> lately to mlx5,
>> Maybe something changed in the stack ?
>>
>> what configuration are you running ? what traffic ?
>>
> Nothing fancy. 8 queues and 20 concurrent netperf TCP_STREAMs trips
> it. Not a lot of them, but I don't think we really should ever see
> these errors.
>
Hi Tom
I've been trying to repro with no luck with kernel v4.9.
I am looking for checksum errors in dmesg, is that the place where you
saw the errors ?
can you dump the error in here ?
Powered by blists - more mailing lists