public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH 1/1] io_uring/rw: reissue only from the same task
Date: Tue, 7 Jan 2025 07:31:34 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <e769b0d12b3c70861c2144b3ea58d3f08d542bbc.1736259071.git.asml.silence@gmail.com>

On 1/7/25 7:11 AM, Pavel Begunkov wrote:
> io_rw_should_reissue() tries to propagate EAGAIN back to io_uring when
> happens off the submission path, which is when it's staying within the
> same task, and so thread group checks don't make much sense.

Since there's the nvme multipath retry issue, let's skip this for now
and focus on sanitizing the retry stuff for 6.14 with an eye towards
just backporting that to 6.10+ where we have some sanity on the
import side with persistent data across issues.

-- 
Jens Axboe


  reply	other threads:[~2025-01-07 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 14:11 [PATCH 1/1] io_uring/rw: reissue only from the same task Pavel Begunkov
2025-01-07 14:31 ` Jens Axboe [this message]
2025-01-07 18:01   ` 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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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