From: Ian Kumlien <ian.kumlien@gmail.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Saeed Mahameed <saeedm@mellanox.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [ISSUE][4.20.6] mlx5 and checksum failures
Date: Thu, 7 Feb 2019 00:00:17 +0100 [thread overview]
Message-ID: <CAA85sZup2UHbCX1KZ5bJNv=f=aoXrTz_0sjDUQ0fRRfU+fVSeA@mail.gmail.com> (raw)
In-Reply-To: <CAM_iQpWMdMG_wtvHa9NQHQnQ4AuEEH2FcsJ2nWptSqFD_-6-Ww@mail.gmail.com>
On Wed, Feb 6, 2019 at 11:49 PM Cong Wang <xiyou.wangcong@gmail.com> wrote:
>
> On Wed, Feb 6, 2019 at 2:41 PM Ian Kumlien <ian.kumlien@gmail.com> wrote:
> >
> > On Wed, Feb 6, 2019 at 11:38 PM Cong Wang <xiyou.wangcong@gmail.com> wrote:
> > > On Wed, Feb 6, 2019 at 2:15 PM Ian Kumlien <ian.kumlien@gmail.com> wrote:
> > > > Could we please schedule this for 4.19 and 4.20 - it's kinda breaking things
> > >
> > > It doesn't break anything, packets are _not_ dropped, only that the
> > > warning itself is noisy.
> >
> > Not my experience, to me it slows the machine down and looses packets,
> > I don't however know
> > if this is the only culprit
>
> The packet process could be slow down because of printing
> out this kernel warning. Packet should be still delivered to upper
> stack, at least I didn't see any packet drops because of this.
I have several machines pushing the same errors currently, while on this
one I was logged in on the serial console and not over ssh like the others.
On the other machines, typing is slow, looses characters and drops the
connection
But, again, I don't know if this is the only culprit, it sure does
fill dmesg though =)
(which suddenly takes minutes to show over a 100gig connection)
> > You can actually see it on ping where it start out with 0.0xyx and
> > ends up at ~10ms
>
> I don't understand how it could affect ICMP, it is purely TCP
> from my point of view, even the stack trace from you says so. ;)
It changes directly after the first hw checksum failure, I don't know why =/
next prev parent reply other threads:[~2019-02-06 23:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 16:16 [ISSUE][4.20.6] mlx5 and checksum failures Ian Kumlien
2019-02-06 17:18 ` Saeed Mahameed
2019-02-06 22:03 ` David Miller
2019-02-06 22:12 ` Ian Kumlien
2019-02-06 22:22 ` David Miller
2019-02-06 22:33 ` Ian Kumlien
2019-02-06 22:38 ` Cong Wang
2019-02-06 22:41 ` Ian Kumlien
2019-02-06 22:49 ` Cong Wang
2019-02-06 23:00 ` Ian Kumlien [this message]
2019-02-07 1:00 ` Saeed Mahameed
2019-02-07 10:16 ` Ian Kumlien
2019-02-07 18:42 ` Saeed Mahameed
2019-02-07 22:01 ` Ian Kumlien
2019-02-08 16:29 ` Ian Kumlien
2019-02-09 15:54 ` Ian Kumlien
2019-02-13 12:04 ` Ian Kumlien
2019-02-13 23:36 ` Saeed Mahameed
2019-02-07 21:40 ` Marcelo Ricardo Leitner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA85sZup2UHbCX1KZ5bJNv=f=aoXrTz_0sjDUQ0fRRfU+fVSeA@mail.gmail.com' \
--to=ian.kumlien@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).