XDP Newbie developer discussions
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Eric Leblond <eric@regit.org>, xdp-newbies@vger.kernel.org
Subject: Re: AF_XDP and packet timestamp
Date: Mon, 17 Jun 2019 13:03:14 +0200	[thread overview]
Message-ID: <87d0jca2z1.fsf@toke.dk> (raw)
In-Reply-To: <86f135475a7820adadb05e7ac9a05c71846bebd6.camel@regit.org>

Eric Leblond <eric@regit.org> writes:

> Hello,
>
> I did start to work on AF_XDP support for Suricata. API was really easy
> to use via libbpf.
>
> From Suricata point of view, the current system with default
> configuration is lacking an important information. I don't have access
> to the timestamp of the packet. I'm in particular interested by the
> hardware timestamp as it would allow to do reordering in some capture
> cases.
>
> Is there a way to get the information via AF_XDP. I've seen the
> discussion on hardware hints but there was no code example I was able
> to find.

Making more information from the hardware available to XDP is currently
on our list of things we plan to enable in the future:
https://github.com/xdp-project/xdp-project/blob/master/xdp-project.org#metadata-available-to-programs

I just added timestamps as a field we want in there (so we don't
forget).

I.e., no, there is no way to get this information from XDP (and thus not
from AF_XDP either) yet...

-Toke

  parent reply	other threads:[~2019-06-17 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 10:00 AF_XDP and packet timestamp Eric Leblond
2019-06-17 10:57 ` Ilias Apalodimas
2019-06-17 11:03 ` Toke Høiland-Jørgensen [this message]
2019-07-21  6:42   ` 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=87d0jca2z1.fsf@toke.dk \
    --to=toke@redhat.com \
    --cc=eric@regit.org \
    --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