From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@google.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
haoluo@google.com, jolsa@kernel.org, jbrouer@redhat.com
Subject: Re: [PATCH bpf-next v2] selftests/bpf: Properly enable hwtstamp in xdp_hw_metadata
Date: Fri, 27 Jan 2023 07:20:24 +0000 [thread overview]
Message-ID: <167480402468.13293.11999774321675833770.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230126225030.510629-1-sdf@google.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Thu, 26 Jan 2023 14:50:30 -0800 you wrote:
> The existing timestamping_enable() is a no-op because it applies
> to the socket-related path that we are not verifying here
> anymore. (but still leaving the code around hoping we can
> have xdp->skb path verified here as well)
>
> poll: 1 (0)
> xsk_ring_cons__peek: 1
> 0xf64788: rx_desc[0]->addr=100000000008000 addr=8100 comp_addr=8000
> rx_hash: 3697961069
> rx_timestamp: 1674657672142214773 (sec:1674657672.1422)
> XDP RX-time: 1674657709561774876 (sec:1674657709.5618) delta sec:37.4196
> AF_XDP time: 1674657709561871034 (sec:1674657709.5619) delta
> sec:0.0001 (96.158 usec)
> 0xf64788: complete idx=8 addr=8000
>
> [...]
Here is the summary with links:
- [bpf-next,v2] selftests/bpf: Properly enable hwtstamp in xdp_hw_metadata
https://git.kernel.org/bpf/bpf-next/c/a5f3a3f7c172
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-01-27 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 22:50 [PATCH bpf-next v2] selftests/bpf: Properly enable hwtstamp in xdp_hw_metadata Stanislav Fomichev
2023-01-27 7:20 ` patchwork-bot+netdevbpf [this message]
2023-01-27 13:36 ` Jesper Dangaard Brouer
2023-01-27 17:09 ` Stanislav Fomichev
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=167480402468.13293.11999774321675833770.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=jbrouer@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.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