From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: "Deric, Nemanja" <nemanja.deric@siemens.com>,
"xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>
Cc: "Bezdeka, Florian" <florian.bezdeka@siemens.com>,
Magnus Karlsson <magnus.karlsson@gmail.com>
Subject: Re: Questions regarding AF_XDP (ETF, TX queue selection)
Date: Sat, 09 Apr 2022 15:00:40 +0200 [thread overview]
Message-ID: <878rse8l8n.fsf@toke.dk> (raw)
In-Reply-To: <DB6PR10MB1558DC7F6B10FD08418EC505EAE99@DB6PR10MB1558.EURPRD10.PROD.OUTLOOK.COM>
"Deric, Nemanja" <nemanja.deric@siemens.com> writes:
> 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?
Your understanding is basically correct: there's currently no support
for that kind of metadata in XDP at all (which extends to AF_XDP). The
effort to fix that is xdp-hints, and timestamps are explicitly part of
that. That's still work in progress; there's a mailing list dedicated
to this that you may want to subscribe to (and feel free to send a
message there indicating your interest!):
https://lists.xdp-project.net/postorius/lists/xdp-hints.xdp-project.net/
The closest you can get to a "progress report" is probably looking
through the archive of that list.
> 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?
+Magnus who may have an idea about this.
-Toke
next prev parent reply other threads:[~2022-04-09 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 15:26 Questions regarding AF_XDP (ETF, TX queue selection) Deric, Nemanja
2022-04-09 13:00 ` Toke Høiland-Jørgensen [this message]
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=878rse8l8n.fsf@toke.dk \
--to=toke@redhat.com \
--cc=florian.bezdeka@siemens.com \
--cc=magnus.karlsson@gmail.com \
--cc=nemanja.deric@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).