public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: [PATCH RFC] io_uring: remove retries from io_wq_submit_work()
Date: Mon, 24 Feb 2020 21:33:08 +0300	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


[-- Attachment #1.1: Type: text/plain, Size: 1144 bytes --]

On 24/02/2020 21:16, Jens Axboe wrote:
> On 2/24/20 8:40 AM, Pavel Begunkov wrote:
>> On 24/02/2020 18:27, Jens Axboe wrote:
>>> On 2/24/20 2:15 AM, Pavel Begunkov wrote:
>>>> It seems no opcode may return -EAGAIN for non-blocking case and expect
>>>> to be reissued. Remove retry code from io_wq_submit_work().
>>>
>>> There's actually a comment right there on how that's possible :-)
>>
>> Yeah, I saw it and understand the motive, and how it may happen, but can't
>> find a line, which can actually return -EAGAIN. Could you please point to an
>> example?
> 
> Just give it a whirl, should be easy to reproduce if you just do:
> 
> # echo 2 > /sys/block/nvme0n1/queue/nr_requests
> # fio/t/io_uring /dev/nvme0n1
> 
> or something like that. It's propagated from the kiocb endio handler,
> through, req->result at the bottom of io_issue_sqe()

I see now, thanks! What a jungle

> 
> 	if (ctx->flags & IORING_SETUP_IOPOLL) {
> 		const bool in_async = io_wq_current_is_worker();
> 
> 		if (req->result == -EAGAIN)                                     
> 			return -EAGAIN;
> 	[...]
> 
> 

-- 
Pavel Begunkov


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-02-24 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24  9:15 [PATCH RFC] io_uring: remove retries from io_wq_submit_work() Pavel Begunkov
2020-02-24 15:27 ` Jens Axboe
2020-02-24 15:40   ` Pavel Begunkov
2020-02-24 18:16     ` Jens Axboe
2020-02-24 18:33       ` Pavel Begunkov [this message]
2020-02-24 18:37         ` 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 \
    [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