netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: rawip: delayed and mis-sequenced transmits
Date: Wed, 6 Jul 2022 18:54:17 -0700	[thread overview]
Message-ID: <20220706185417.2fcbcdf0@kernel.org> (raw)
In-Reply-To: <433be56da42f4ab2b7722c1caed3a747@AcuMS.aculab.com>

On Wed, 6 Jul 2022 15:54:18 +0000 David Laight wrote:
> Anyone any ideas before I start digging through the kernel code?

If the qdisc is pfifo_fast and kernel is old there could be races.
But I don't think that's likely given you probably run something
recent and next packet tx would usually flush the stuck packet.
In any case - switching qdisc could be a useful test, also bpftrace 
is your friend for catching patckets with long sojourn time.

  reply	other threads:[~2022-07-07  1:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 15:54 rawip: delayed and mis-sequenced transmits David Laight
2022-07-07  1:54 ` Jakub Kicinski [this message]
2022-07-07  8:02   ` David Laight
2022-07-07  9:34   ` David Laight

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=20220706185417.2fcbcdf0@kernel.org \
    --to=kuba@kernel.org \
    --cc=David.Laight@ACULAB.COM \
    --cc=netdev@vger.kernel.org \
    /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).