From: "Deric, Nemanja" <nemanja.deric@siemens.com>
To: "xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>
Cc: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
Subject: Questions regarding AF_XDP (ETF, TX queue selection)
Date: Fri, 8 Apr 2022 15:26:16 +0000 [thread overview]
Message-ID: <DB6PR10MB1558DC7F6B10FD08418EC505EAE99@DB6PR10MB1558.EURPRD10.PROD.OUTLOOK.COM> (raw)
Dear XDP-newbies,
I am Nemanja Deric, and I am working as a Researcher for Industrial
Networking Department of Siemens AG (Munich, Germany). Recently,
we have started looking into AF_XDP/XDP and its applicability for some
of our industrial use cases. Thus, we have a few questions about the
technology which we hope that this mailing list can help us clarify.
If you believe that these questions are better suited for some other
mailing list or direct email contact, please let me know so that I can
contact the correct person/mailing list.
ETF, Timestamping:
In comparison to AF_PACKET sockets AF_XDP sockets do not support
timestamping (SOL_TXTIME) yet. There seems no way to pass such
request or meta-information to the kernel / NIC. Is that correct? We
already heard about "xdp hints" but we have failed to get further
information like plans / roadmap / implementation state / ideas.
Any pointers where to look at?
TX queue selection:
AF_XDP sockets are always bound to a specific RX queue. Instead,
TX queues are "automatically" chosen by the kernel - TX is more or
less handled by NAPI. Correct? Has someone already thought about
TX queue selection? Any plans / roadmap / details according
implementation state available?
In advance, thank you for your help.
Regards,
Nemanja
next reply other threads:[~2022-04-08 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 15:26 Deric, Nemanja [this message]
2022-04-09 13:00 ` Questions regarding AF_XDP (ETF, TX queue selection) Toke Høiland-Jørgensen
2022-04-11 7:39 ` Magnus Karlsson
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=DB6PR10MB1558DC7F6B10FD08418EC505EAE99@DB6PR10MB1558.EURPRD10.PROD.OUTLOOK.COM \
--to=nemanja.deric@siemens.com \
--cc=florian.bezdeka@siemens.com \
--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).