Hi Florian, On Tue Mar 26 2024, Florian Bezdeka wrote: > On Mon, 2024-03-25 at 10:09 +0800, Song Yoong Siang wrote: >> This patch adds support to per-packet Tx hardware timestamp request to >> AF_XDP zero-copy packet via XDP Tx metadata framework. Please note that >> user needs to enable Tx HW timestamp capability via igc_ioctl() with >> SIOCSHWTSTAMP cmd before sending xsk Tx hardware timestamp request. >> >> Same as implementation in RX timestamp XDP hints kfunc metadata, Timer 0 >> (adjustable clock) is used in xsk Tx hardware timestamp. i225/i226 have >> four sets of timestamping registers. *skb and *xsk_tx_buffer pointers >> are used to indicate whether the timestamping register is already occupied. > > Let me make sure that I fully understand that: In my own words: > > With that applied I'm able to get the point in time from the device > when a specific frame made it to the wire. I have to enable that > functionality using the mentioned ioctl() call first, and then check > the meta area (located in the umem right before the frame payload) > while consuming the completion queue/ring. Correct? > > If so, we now have a feedback channel for meta information for/from TX. > Are there any plans - or would it be possible - to support Earliest > TxTime First (NET_SCHED_ETF) QDisc based on that channel? In the past > we had the problem that we we're missing a feedback channel to > communicate back invalid lunch times. Just asking: How would that work? AFAIK XDP bypasses the Qdisc layer. Currently invalid Launch Times are accounted in the ETF Qdisc itself. Does that mean every driver has to take care of it? Thanks, Kurt
Attachment:
signature.asc
Description: PGP signature
