XDP-Newbies Archive mirror
 help / color / mirror / Atom feed
From: Jun Hu <hujun.work@gmail.com>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
	"Konrad Zemek" <konrad@zemek.io>,
	brouer@redhat.com, xdp-newbies@vger.kernel.org,
	"xdp-hints@xdp-project.net" <xdp-hints@xdp-project.net>,
	"Freysteinn Alfredsson" <Freysteinn.Alfredsson@kau.se>
Subject: Re: AF_XDP socket TX path interact with TC?
Date: Wed, 27 Oct 2021 08:48:58 -0700	[thread overview]
Message-ID: <CAEM4-kBiUPF67pnHo3O+7dC8yE8eSgiJ9ZOa4T1MwS-E+wmc6Q@mail.gmail.com> (raw)
In-Reply-To: <ee690d7f-322f-ab51-2c13-06919c10d3ad@redhat.com>

> What is your use-case for adding a TX-timestamp to the packet?
>
> --Jesper
my use case is rather simple, I want to use AF_XDP for traffic tester
type of application, essentially, this application generates testing
traffic, egress via NIC-1, goes into a DUT, and DUT forward the
traffic back into NIC-2, the application need to measure the DUT's
forwarding latency for each packet, so it needs to know the timestamp
of test traffic TX on NIC-1 and RX on NIC-2

                  +-----+
|---------------- | DUT |----------------|
|                 +-----+                |
|                                        |
|          +-------------------+         |
|  <-----  |                   |  <----  |
+----------|NIC-1        NIC-2 |---------+
           |                   |
           +-------------------+

      reply	other threads:[~2021-10-27 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21 22:41 AF_XDP socket TX path interact with TC? Jun Hu
2021-10-25 10:48 ` Toke Høiland-Jørgensen
2021-10-25 18:26   ` Jun Hu
2021-10-26 11:08     ` Konrad Zemek
2021-10-26 18:34       ` Jun Hu
2021-10-27 11:35         ` Toke Høiland-Jørgensen
2021-10-27 14:03           ` Jesper Dangaard Brouer
2021-10-27 15:48             ` Jun Hu [this message]

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=CAEM4-kBiUPF67pnHo3O+7dC8yE8eSgiJ9ZOa4T1MwS-E+wmc6Q@mail.gmail.com \
    --to=hujun.work@gmail.com \
    --cc=Freysteinn.Alfredsson@kau.se \
    --cc=brouer@redhat.com \
    --cc=jbrouer@redhat.com \
    --cc=konrad@zemek.io \
    --cc=toke@redhat.com \
    --cc=xdp-hints@xdp-project.net \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).