LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Jakob Unterwurzacher <jakob.unterwurzacher@theobroma-systems.com> To: John Fastabend <john.fastabend@gmail.com>, Dave Taht <dave.taht@gmail.com> Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, "David S. Miller" <davem@davemloft.net>, "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>, Martin Elshuber <martin.elshuber@theobroma-systems.com> Subject: Re: [bug, bisected] pfifo_fast causes packet reordering Date: Wed, 21 Mar 2018 20:44:04 +0100 [thread overview] Message-ID: <983427eb-2e25-f201-c953-4cff22569deb@theobroma-systems.com> (raw) In-Reply-To: <4e33aae4-9e87-22b4-7f09-008183ea553a@gmail.com> On 21.03.18 19:43, John Fastabend wrote: > Thats my theory at least. Are you able to test a patch if I generate > one to fix this? Yes, no problem. I just tested with the flag change you suggested (see below, I had to keep TCQ_F_CPUSTATS to prevent a crash) and I have NOT seen OOO so far. Thanks, Jakob diff --git a/net/sched/sch_generic.c b/net/sched/sch_generic.c index 190570f21b20..51b68ef4977b 100644 --- a/net/sched/sch_generic.c +++ b/net/sched/sch_generic.c @@ -792,7 +792,7 @@ struct Qdisc_ops pfifo_fast_ops __read_mostly = { .dump = pfifo_fast_dump, .change_tx_queue_len = pfifo_fast_change_tx_queue_len, .owner = THIS_MODULE, - .static_flags = TCQ_F_NOLOCK | TCQ_F_CPUSTATS, + .static_flags = TCQ_F_CPUSTATS, }; EXPORT_SYMBOL(pfifo_fast_ops);
next prev parent reply other threads:[~2018-03-21 19:44 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-13 18:24 [bug, bisected] pfifo_fast causes packet reordering Jakob Unterwurzacher 2018-03-13 18:35 ` Dave Taht 2018-03-14 4:03 ` John Fastabend 2018-03-14 10:09 ` Jakob Unterwurzacher 2018-03-15 18:08 ` Jakob Unterwurzacher 2018-03-15 22:30 ` John Fastabend 2018-03-16 10:26 ` Jakob Unterwurzacher 2018-03-19 6:07 ` Alexander Stein 2018-03-19 12:32 ` Paolo Abeni 2018-03-19 12:56 ` Jakob Unterwurzacher 2018-03-21 10:01 ` Jakob Unterwurzacher 2018-03-21 18:43 ` John Fastabend 2018-03-21 19:44 ` Jakob Unterwurzacher [this message] 2018-03-21 20:52 ` John Fastabend 2018-03-22 10:16 ` Jakob Unterwurzacher 2018-03-24 14:26 ` John Fastabend
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=983427eb-2e25-f201-c953-4cff22569deb@theobroma-systems.com \ --to=jakob.unterwurzacher@theobroma-systems.com \ --cc=dave.taht@gmail.com \ --cc=davem@davemloft.net \ --cc=john.fastabend@gmail.com \ --cc=linux-can@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=martin.elshuber@theobroma-systems.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: linkBe 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).