From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Pavel Begunkov <asml.silence@gmail.com>,
io-uring@vger.kernel.org
Cc: netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Richard Cochran <richardcochran@gmail.com>
Subject: Re: [PATCH v2 5/5] io_uring/netcmd: add tx timestamping cmd support
Date: Thu, 05 Jun 2025 19:54:53 -0400 [thread overview]
Message-ID: <68422e4d1b8ef_208a5f2949@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <584526c3-79f3-42f2-9c6e-4e55ad81b90c@linux.dev>
Vadim Fedorenko wrote:
> On 05/06/2025 01:59, Willem de Bruijn wrote:
> > Pavel Begunkov wrote:
> >> Add a new socket command which returns tx time stamps to the user. It
> >> provide an alternative to the existing error queue recvmsg interface.
> >> The command works in a polled multishot mode, which means io_uring will
> >> poll the socket and keep posting timestamps until the request is
> >> cancelled or fails in any other way (e.g. with no space in the CQ). It
> >> reuses the net infra and grabs timestamps from the socket's error queue.
> >>
> >> The command requires IORING_SETUP_CQE32. All non-final CQEs (marked with
> >> IORING_CQE_F_MORE) have cqe->res set to the tskey, and the upper 16 bits
> >> of cqe->flags keep tstype (i.e. offset by IORING_CQE_BUFFER_SHIFT). The
> >> timevalue is store in the upper part of the extended CQE. The final
> >> completion won't have IORING_CQR_F_MORE and will have cqe->res storing
> >> 0/error.
> >>
> >> Suggested-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
> >> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
> >> ---
> >> include/uapi/linux/io_uring.h | 6 +++
> >> io_uring/cmd_net.c | 77 +++++++++++++++++++++++++++++++++++
> >> 2 files changed, 83 insertions(+)
> >>
> >> diff --git a/include/uapi/linux/io_uring.h b/include/uapi/linux/io_uring.h
> >> index cfd17e382082..0bc156eb96d4 100644
> >> --- a/include/uapi/linux/io_uring.h
> >> +++ b/include/uapi/linux/io_uring.h
> >> @@ -960,6 +960,11 @@ struct io_uring_recvmsg_out {
> >> __u32 flags;
> >> };
> >>
> >> +struct io_timespec {
> >> + __u64 tv_sec;
> >> + __u64 tv_nsec;
> >> +};
> >> +
> >> /*
> >> * Argument for IORING_OP_URING_CMD when file is a socket
> >> */
> >> @@ -968,6 +973,7 @@ enum io_uring_socket_op {
> >> SOCKET_URING_OP_SIOCOUTQ,
> >> SOCKET_URING_OP_GETSOCKOPT,
> >> SOCKET_URING_OP_SETSOCKOPT,
> >> + SOCKET_URING_OP_TX_TIMESTAMP,
> >> };
> >>
> >> /* Zero copy receive refill queue entry */
> >> diff --git a/io_uring/cmd_net.c b/io_uring/cmd_net.c
> >> index e99170c7d41a..dae59aea5847 100644
> >> --- a/io_uring/cmd_net.c
> >> +++ b/io_uring/cmd_net.c
> >> @@ -1,5 +1,6 @@
> >> #include <asm/ioctls.h>
> >> #include <linux/io_uring/net.h>
> >> +#include <linux/errqueue.h>
> >> #include <net/sock.h>
> >>
> >> #include "uring_cmd.h"
> >> @@ -51,6 +52,80 @@ static inline int io_uring_cmd_setsockopt(struct socket *sock,
> >> optlen);
> >> }
> >>
> >> +static bool io_process_timestamp_skb(struct io_uring_cmd *cmd, struct sock *sk,
> >> + struct sk_buff *skb, unsigned issue_flags)
> >> +{
> >> + struct sock_exterr_skb *serr = SKB_EXT_ERR(skb);
> >> + struct io_uring_cqe cqe[2];
> >> + struct io_timespec *iots;
> >> + struct timespec64 ts;
> >> + u32 tskey;
> >> +
> >> + BUILD_BUG_ON(sizeof(struct io_uring_cqe) != sizeof(struct io_timespec));
> >> +
> >> + if (!skb_get_tx_timestamp(skb, sk, &ts))
> >> + return false;
> >> +
> >> + tskey = serr->ee.ee_data;
> >> +
> >> + cqe->user_data = 0;
> >> + cqe->res = tskey;
> >> + cqe->flags = IORING_CQE_F_MORE;
> >> + cqe->flags |= (u32)serr->ee.ee_info << IORING_CQE_BUFFER_SHIFT;
> >> +
> >> + iots = (struct io_timespec *)&cqe[1];
> >> + iots->tv_sec = ts.tv_sec;
> >> + iots->tv_nsec = ts.tv_nsec;
> >
> > skb_get_tx_timestamp loses the information whether this is a
> > software or a hardware timestamp. Is that loss problematic?
> >
> > If a process only requests one type of timestamp, it will not be.
> >
> > But when requesting both (SOF_TIMESTAMPING_OPT_TX_SWHW) this per cqe
> > annotation may be necessary.
>
> skb_has_tx_timestamp() helper has clear priority of software timestamp,
> if enabled for the socket. Looks like SOF_TIMESTAMPING_OPT_TX_SWHW case
> won't produce both timestamps with the current implementation. Am I
> missing something?
The point of that option is to request both SW and HW tx
timestamps. Before that option, the SW timestamp was suppressed if a
HW timestamp was pending.
The io_uring API as currently written will again return only one
timestamp, but this time the SW one.
If the user explicitly sets SOF_TIMESTAMPING_OPT_TX_SWHW, they will
want both, and want to be able to disambiguate them.
next prev parent reply other threads:[~2025-06-05 23:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 8:42 [PATCH v2 0/5] io_uring cmd for tx timestamps Pavel Begunkov
2025-06-04 8:42 ` [PATCH v2 1/5] net: timestamp: add helper returning skb's tx tstamp Pavel Begunkov
2025-06-04 15:37 ` Stanislav Fomichev
2025-06-05 0:52 ` Willem de Bruijn
2025-06-05 3:51 ` Jason Xing
2025-06-04 8:42 ` [PATCH v2 2/5] io_uring/poll: introduce io_arm_apoll() Pavel Begunkov
2025-06-04 8:42 ` [PATCH v2 3/5] io_uring/cmd: allow multishot polled commands Pavel Begunkov
2025-06-04 8:42 ` [PATCH v2 4/5] io_uring: add mshot helper for posting CQE32 Pavel Begunkov
2025-06-04 8:42 ` [PATCH v2 5/5] io_uring/netcmd: add tx timestamping cmd support Pavel Begunkov
2025-06-04 12:04 ` Jens Axboe
2025-06-04 12:33 ` Pavel Begunkov
2025-06-05 0:59 ` Willem de Bruijn
2025-06-05 10:25 ` Vadim Fedorenko
2025-06-05 11:01 ` Pavel Begunkov
2025-06-05 23:54 ` Willem de Bruijn [this message]
2025-06-06 0:17 ` Jason Xing
2025-06-06 0:02 ` Jason Xing
2025-06-06 8:12 ` Pavel Begunkov
2025-06-06 8:33 ` Jason Xing
2025-06-06 9:08 ` Pavel Begunkov
2025-06-04 8:53 ` [PATCH v2 0/5] io_uring cmd for tx timestamps Pavel Begunkov
2025-06-04 12:06 ` Jens Axboe
2025-06-04 12:38 ` Pavel Begunkov
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=68422e4d1b8ef_208a5f2949@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=io-uring@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
--cc=willemb@google.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