From: Jesper Dangaard Brouer <hawk@kernel.org>
To: Stanislav Fomichev <sdf@google.com>
Cc: hawk@kernel.org, Arun Thomas <arthomas@redhat.com>,
"Song, Yoong Siang" <yoong.siang.song@intel.com>,
"Abdul Rahim, Faizal" <faizal.abdul.rahim@intel.com>,
Fabien Dupont <fdupont@redhat.com>,
"Chavez, Robert" <robert.chavez@intel.com>,
Zaremba Larysa <larysa.zaremba@intel.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <borkmann@iogearbox.net>,
Costin Gament <cgament@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Felix Maurer <fmaurer@redhat.com>,
"Desouza, Ederson" <ederson.desouza@intel.com>,
Kishen Maloor <kishen.maloor@intel.com>,
"xdp-hints@xdp-project.net" <xdp-hints@xdp-project.net>
Subject: [xdp-hints] Interest in TX-side XDP metadata hints from Intel (+ Red Hat)
Date: Fri, 8 Sep 2023 16:18:11 +0200 [thread overview]
Message-ID: <52272237-a3cd-23a4-cbc7-e6a53cbf2c85@kernel.org> (raw)
Hi Stanislav,
Sharing that Intel (+Red Hat) have an interest in getting XDP metadata
hints working on smaller devices used for "Edge Controls for Industrial"
(ECI)[1].
What are your plans for your patchset[2] ?
My suggestion (to Intel) is that we implement the TX-timestamp (plus
LaunchTime) on top of Stanslav's patches[2]. For drivers igc+igb+stmmac
which I think will cover the tests[3] need by Arun/Costin (?). And then
post it upstream for review.
The Intel test tool[3] isn't open, but it is an AF_XDP based Real-Time
Compute Performance (RTCP) application that show-case a real-time
control loop application. The current code uses out-of-tree[4] "TXTIME"
LaunchTime feature, that want not upstreamed.
Lets us instead implement a proper TX LaunchTime feature on top of [2].
--Jesper
cc. XDP-hints ML as anyone is free to code this up, code help here[5]
[1] https://eci.intel.com/
[2] https://lore.kernel.org/all/20230809165418.2831456-1-sdf@google.com/
[3] https://github.com/OTCShare2/rtcp-xdp
[4] https://lore.kernel.org/all/20210621230635.3a83851c@carbon/
[5]
https://github.com/xdp-project/xdp-project/blob/master/areas/tsn/code01_follow_qdisc_TSN_offload.org#tx-time-to-hardware-driver-igc
next reply other threads:[~2023-09-08 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 14:18 Jesper Dangaard Brouer [this message]
2023-09-08 16:37 ` [xdp-hints] " Stanislav Fomichev
2023-09-14 1:22 ` Song, Yoong Siang
2023-09-14 21:05 ` Stanislav Fomichev
2023-09-21 2:10 ` Song, Yoong Siang
2023-09-21 4:35 ` Stanislav Fomichev
2023-09-21 8:17 ` Song, Yoong Siang
2023-09-21 16:24 ` Stanislav Fomichev
2023-09-22 0:16 ` Song, Yoong Siang
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
List information: https://lists.xdp-project.net/postorius/lists/xdp-hints.xdp-project.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52272237-a3cd-23a4-cbc7-e6a53cbf2c85@kernel.org \
--to=hawk@kernel.org \
--cc=arthomas@redhat.com \
--cc=ast@kernel.org \
--cc=borkmann@iogearbox.net \
--cc=bristot@redhat.com \
--cc=cgament@redhat.com \
--cc=ederson.desouza@intel.com \
--cc=faizal.abdul.rahim@intel.com \
--cc=fdupont@redhat.com \
--cc=fmaurer@redhat.com \
--cc=kishen.maloor@intel.com \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=robert.chavez@intel.com \
--cc=sdf@google.com \
--cc=xdp-hints@xdp-project.net \
--cc=yoong.siang.song@intel.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