All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>,
	io-uring@vger.kernel.org,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: netdev@vger.kernel.org, Eric Dumazet <edumazet@google.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>,
	Stanislav Fomichev <sdf@fomichev.me>,
	Jason Xing <kerneljasonxing@gmail.com>,
	Kuniyuki Iwashima <kuniyu@google.com>
Subject: Re: (subset) [PATCH v5 0/5] io_uring cmd for tx timestamps
Date: Sat, 28 Jun 2025 07:10:36 +0100	[thread overview]
Message-ID: <cf277ccc-5228-41dc-abd5-d486244682dd@gmail.com> (raw)
In-Reply-To: <a3e2d283-37cd-4c96-ab0b-dfd1c50aae61@kernel.dk>

On 6/27/25 18:07, Jens Axboe wrote:
> On 6/23/25 9:01 AM, Jens Axboe wrote:
>>
>> On Mon, 16 Jun 2025 10:46:24 +0100, Pavel Begunkov wrote:
>>> Vadim Fedorenko suggested to add an alternative API for receiving
>>> tx timestamps through io_uring. The series introduces io_uring socket
>>> cmd for fetching tx timestamps, which is a polled multishot request,
>>> i.e. internally polling the socket for POLLERR and posts timestamps
>>> when they're arrives. For the API description see Patch 5.
>>>
>>> It reuses existing timestamp infra and takes them from the socket's
>>> error queue. For networking people the important parts are Patch 1,
>>> and io_uring_cmd_timestamp() from Patch 5 walking the error queue.
>>>
>>> [...]
>>
>> Applied, thanks!
>>
>> [2/5] io_uring/poll: introduce io_arm_apoll()
>>        commit: 162151889267089bb920609830c35f9272087c3f
>> [3/5] io_uring/cmd: allow multishot polled commands
>>        commit: b95575495948a81ac9b0110aa721ea061dd850d9
>> [4/5] io_uring: add mshot helper for posting CQE32
>>        commit: ac479eac22e81c0ff56c6bdb93fad787015149cc
>> [5/5] io_uring/netcmd: add tx timestamping cmd support
>>        commit: 9e4ed359b8efad0e8ad4510d8ad22bf0b060526a
> 
> Pavel, can you send in the liburing PR for these, please?

It needs a minor clean up, I'll send it by Monday

-- 
Pavel Begunkov


  reply	other threads:[~2025-06-28  6:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  9:46 [PATCH v5 0/5] io_uring cmd for tx timestamps Pavel Begunkov
2025-06-16  9:46 ` [PATCH v5 1/5] net: timestamp: add helper returning skb's tx tstamp Pavel Begunkov
2025-06-16 14:53   ` Willem de Bruijn
2025-06-16 15:01   ` Willem de Bruijn
2025-06-16 16:37     ` Pavel Begunkov
2025-06-16 16:43       ` Willem de Bruijn
2025-06-17 16:30     ` Willem de Bruijn
2025-06-18  7:01   ` Jason Xing
2025-06-16  9:46 ` [PATCH v5 2/5] io_uring/poll: introduce io_arm_apoll() Pavel Begunkov
2025-06-16  9:46 ` [PATCH v5 3/5] io_uring/cmd: allow multishot polled commands Pavel Begunkov
2025-06-16  9:46 ` [PATCH v5 4/5] io_uring: add mshot helper for posting CQE32 Pavel Begunkov
2025-06-16  9:46 ` [PATCH v5 5/5] io_uring/netcmd: add tx timestamping cmd support Pavel Begunkov
2025-06-17 14:52 ` [PATCH v5 0/5] io_uring cmd for tx timestamps Jens Axboe
2025-06-17 22:29   ` Jakub Kicinski
2025-06-17 22:33     ` Jens Axboe
2025-06-17 22:41       ` Jakub Kicinski
2025-06-17 22:41         ` Jens Axboe
2025-06-20 14:31         ` Jens Axboe
2025-06-20 16:30           ` Pavel Begunkov
2025-06-20 19:46           ` Jakub Kicinski
2025-06-21  0:45             ` Jens Axboe
2025-06-23 15:00             ` Jens Axboe
2025-06-23 15:01 ` (subset) " Jens Axboe
2025-06-27 17:07   ` Jens Axboe
2025-06-28  6:10     ` Pavel Begunkov [this message]
2025-07-08 17:55       ` Jens Axboe
2025-07-08 18:00         ` Pavel Begunkov
2025-07-08 18:00           ` Jens Axboe

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=cf277ccc-5228-41dc-abd5-d486244682dd@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=io-uring@vger.kernel.org \
    --cc=kerneljasonxing@gmail.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=sdf@fomichev.me \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.