public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Xie Maoyi <maoyi.xie@ntu.edu.sg>,
	Pavel Begunkov <asml.silence@gmail.com>
Cc: Andrei Vagin <avagin@gmail.com>,
	"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: io_uring: should IORING_TIMEOUT_ABS honour the submitter's time namespace?
Date: Mon, 4 May 2026 01:34:38 -0600	[thread overview]
Message-ID: <393cb843-a625-4a7d-9817-be77cfc50037@kernel.dk> (raw)
In-Reply-To: <OS8PR01MB674993B75C46D1763F925ADDDC312@OS8PR01MB6749.apcprd01.prod.exchangelabs.com>

On 5/4/26 1:23 AM, Xie Maoyi wrote:
> On 5/3/26, Jens Axboe wrote:
>> Might make sense to refactor a helper that does the time translation,
>> and then patch 1 would basically be Pavel's fix and patch 2 would be
>> sorting out the io_cqring_wait() translation as well. Both should be
>> able to use the refactored helper.
> 
> Understood. I will prepare a 2-patch series along those lines:
> 
>   1/2 io_uring: introduce io_timens_to_host_ktime() helper and apply
>         it in IORING_OP_TIMEOUT / IORING_OP_LINK_TIMEOUT (= Pavel's
>         fix for io_parse_user_time).
> 
>   2/2 io_uring: route io_uring_enter()'s IORING_ENTER_ABS_TIMER path
>         through the same helper (covers io_uring/wait.c around the
>         ext_arg->ts parse).

Sounds good.

> Could you point me at the right base to develop on top of? Pavel's
> draft uses io_parse_user_time which is not in v7.0 mainline, so I
> assume the target is one of the io_uring trees (for-next?). I will
> also re-run the SQPOLL and ABS_TIMER reproducers against the
> series before sending.

Right, that helper landed in 7.1-rc, it's not in 7.0. Use my
io_uring-7.1 branch and we can land this in 7.1, and then for the stable
backports we just pull in the helper that you already have in 7.1. By
definition, work can only go into the currently open branch, which is
7.1. Anything else has to be stable backports.

-- 
Jens Axboe

  reply	other threads:[~2026-05-04  7:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-02  9:21 io_uring: should IORING_TIMEOUT_ABS honour the submitter's time namespace? Xie Maoyi
2026-05-02 10:26 ` Pavel Begunkov
     [not found]   ` <TYZPR01MB6758466089A9CAADC5095F20DC332@TYZPR01MB6758.apcprd01.prod.exchangelabs.com>
2026-05-03 15:12     ` Xie Maoyi
2026-05-04  6:06       ` Jens Axboe
2026-05-04  7:23         ` Xie Maoyi
2026-05-04  7:34           ` Jens Axboe [this message]
2026-05-04  7:48         ` Pavel Begunkov
2026-05-04 10:02           ` 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=393cb843-a625-4a7d-9817-be77cfc50037@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --cc=avagin@gmail.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maoyi.xie@ntu.edu.sg \
    /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