From: Jakob Unterwurzacher <jakob.unterwurzacher@theobroma-systems.com>
To: Paolo Abeni <pabeni@redhat.com>,
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: Mon, 19 Mar 2018 13:56:47 +0100 [thread overview]
Message-ID: <5468f8eb-17b6-9000-ab4d-a2c67ef35e4b@theobroma-systems.com> (raw)
In-Reply-To: <1521462750.3059.12.camel@redhat.com>
On 19.03.18 13:32, Paolo Abeni wrote:
> Is not clear to me if you can reproduce the bug with the vanilla
> kernel, or if you need some out-of-tree nic driver. Can you please
> clarify which NIC/driver are you using?
Yes I reproduced it with a vanilla kernel. I use two off-the-shelf USB
NICs, lsusb says:
Bus 005 Device 013: ID 0b95:7720 ASIX Electronics Corp. AX88772
Bus 005 Device 014: ID 0b95:772b ASIX Electronics Corp. AX88772B
Photo of the setup:
https://github.com/jakob-tsd/pfifo_stress/blob/master/usb_nics.jpg
Best regards,
Jakob
next prev parent reply other threads:[~2018-03-19 12:56 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 [this message]
2018-03-21 10:01 ` Jakob Unterwurzacher
2018-03-21 18:43 ` John Fastabend
2018-03-21 19:44 ` Jakob Unterwurzacher
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=5468f8eb-17b6-9000-ab4d-a2c67ef35e4b@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 \
--cc=pabeni@redhat.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).