From: "Gaul, Maximilian" <maximilian.gaul@hm.edu>
To: Xdp <xdp-newbies@vger.kernel.org>
Subject: AW: Intel 10G 2P X520 Adapter doesn't receive anything with AF XDP
Date: Thu, 4 Jun 2020 20:06:38 +0000 [thread overview]
Message-ID: <be214a8beb65491eb69333eb29eca537@hm.edu> (raw)
In-Reply-To: <7ec53b8f30524ffba36bb264c6d023fc@hm.edu>
> Best regards
>
> Max
A small update. I disabled the ethtool ntuple rule which steers the multicast packets to a specific RX-Queue and let the program run for 2 minutes.
After 2 minutes or so I looked at the BPF map again and saw this:
$ sudo bpftool map dump id 41
key: 00 00 00 00 value: eb 00 00 00 00 00 00 00
key: 01 00 00 00 value: 6b 00 00 00 00 00 00 00
key: 02 00 00 00 value: 18 00 00 00 00 00 00 00
key: 03 00 00 00 value: 01 00 00 00 00 00 00 00
key: 04 00 00 00 value: 17 00 00 00 00 00 00 00
key: 05 00 00 00 value: 3a 00 00 00 00 00 00 00
key: 06 00 00 00 value: 65 00 00 00 00 00 00 00
key: 07 00 00 00 value: 3c 7a 89 01 00 00 00 00
key: 08 00 00 00 value: 02 00 00 00 00 00 00 00
key: 09 00 00 00 value: 12 00 00 00 00 00 00 00
key: 0a 00 00 00 value: 55 00 00 00 00 00 00 00
key: 0b 00 00 00 value: 14 00 00 00 00 00 00 00
key: 0c 00 00 00 value: 2c 00 00 00 00 00 00 00
key: 0d 00 00 00 value: 00 00 00 00 00 00 00 00
key: 0e 00 00 00 value: 1b 00 00 00 00 00 00 00
As you can see, the multicast stream is probably landing on RX-Queue 7 (unfortunately my XSK-Program is waiting for packets on RX-Queue 0) but somehow delayed for 1 or 2 minutes.
In case I enable ntuple via
ethtool -K eth5 ntuple on
and add the ethtool ntuple rule back, wait for 2 minutes again, I get this:
$ sudo bpftool map dump id 46
key: 00 00 00 00 value: 6f 16 00 00 00 00 00 00
key: 01 00 00 00 value: 43 00 00 00 00 00 00 00
key: 02 00 00 00 value: 0d 00 00 00 00 00 00 00
key: 03 00 00 00 value: 00 00 00 00 00 00 00 00
key: 04 00 00 00 value: 0e 00 00 00 00 00 00 00
key: 05 00 00 00 value: 24 00 00 00 00 00 00 00
key: 06 00 00 00 value: 34 00 00 00 00 00 00 00
key: 07 00 00 00 value: 7d 05 00 00 00 00 00 00
key: 08 00 00 00 value: 01 00 00 00 00 00 00 00
key: 09 00 00 00 value: 0a 00 00 00 00 00 00 00
key: 0a 00 00 00 value: 30 00 00 00 00 00 00 00
key: 0b 00 00 00 value: 0e 00 00 00 00 00 00 00
key: 0c 00 00 00 value: 1b 00 00 00 00 00 00 00
key: 0d 00 00 00 value: 00 00 00 00 00 00 00 00
key: 0e 00 00 00 value: 0a 00 00 00 00 00 00 00
As you can see, no indicator for a multicast stream with lots of packets :(
Something is wrong here...
prev parent reply other threads:[~2020-06-04 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 19:25 Intel 10G 2P X520 Adapter doesn't receive anything with AF XDP Gaul, Maximilian
2020-06-04 20:06 ` Gaul, Maximilian [this message]
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=be214a8beb65491eb69333eb29eca537@hm.edu \
--to=maximilian.gaul@hm.edu \
--cc=xdp-newbies@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).