public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Fomichev <sdf@google.com>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] XDP metadata for TX
Date: Thu, 23 Feb 2023 14:23:34 -0800	[thread overview]
Message-ID: <Y/fnZkXQdc8lkP7q@google.com> (raw)

I'd like to discuss a potential follow up for the previous "XDP RX
metadata" series [0].

Now that we can access (a subset of) packet metadata at RX, I'd like to
explore the options where we can export some of that metadata on TX. And
also whether it might be possible to access some of the TX completion
metadata (things like TX timestamp).

I'm currently trying to understand whether the same approach I've used
on RX could work at TX. By May I plan to have a bunch of options laid
out (currently considering XSK tx/compl programs and XDP tx/compl
programs) so we have something to discuss.

I'd like to some more input on whether applying the same idea on TX
makes sense or not and whether there are any sensible alternatives.
(IIRC, there was an attempt to do XDP on egress that went nowhere).

0: https://lore.kernel.org/bpf/20230119221536.3349901-1-sdf@google.com/

             reply	other threads:[~2023-02-23 22:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 22:23 Stanislav Fomichev [this message]
2023-02-23 23:22 ` [LSF/MM/BPF TOPIC] XDP metadata for TX Toke Høiland-Jørgensen
2023-02-23 23:51   ` Stanislav Fomichev
2023-02-27 14:17     ` Toke Høiland-Jørgensen
2023-02-27 20:03       ` Stanislav Fomichev
2023-02-27 23:54         ` Toke Høiland-Jørgensen
2023-02-28 21:18           ` Stanislav Fomichev
2023-02-28 22:09             ` Toke Høiland-Jørgensen
2023-02-28 23:02               ` Stanislav Fomichev
2023-02-28 23:08                 ` Toke Høiland-Jørgensen
2023-03-03  7:42         ` Magnus Karlsson
2023-03-03 12:37           ` Toke Høiland-Jørgensen
2023-03-03 17:16             ` Stanislav Fomichev
2023-03-07 19:32           ` Jesper Dangaard Brouer
2023-03-09 18:04             ` Stanislav Fomichev
2023-03-10 11:09               ` Jesper Dangaard Brouer

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=Y/fnZkXQdc8lkP7q@google.com \
    --to=sdf@google.com \
    --cc=bpf@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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