public inbox for [email protected]
 help / color / mirror / Atom feed
From: Hao Xu <[email protected]>
To: Pavel Begunkov <[email protected]>,
	Jens Axboe <[email protected]>, io-uring <[email protected]>
Subject: Re: [PATCH] io_uring: don't mark S_ISBLK async work as unbounded
Date: Tue, 6 Apr 2021 00:13:32 +0800	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

在 2021/4/4 下午7:02, Pavel Begunkov 写道:
> On 04/04/2021 11:57, Hao Xu wrote:
>> 在 2021/4/2 下午6:48, Pavel Begunkov 写道:
>>> On 02/04/2021 11:32, Pavel Begunkov wrote:
>>>> On 02/04/2021 09:52, Hao Xu wrote:
>>>>> 在 2021/4/1 下午10:57, Jens Axboe 写道:
>>>>>> S_ISBLK is marked as unbounded work for async preparation, because it
>>>>>> doesn't match S_ISREG. That is incorrect, as any read/write to a block
>>>>>> device is also a bounded operation. Fix it up and ensure that S_ISBLK
>>>>>> isn't marked unbounded.
>>>>>>
>>>>>> Signed-off-by: Jens Axboe <[email protected]>
>>>>>>
>>>>> Hi Jens, I saw a (un)bounded work is for a (un)bounded worker to
>>>>> execute. What is the difference between bounded and unbounded?
>>>>
>>>> Unbounded works are not bounded in execution time, i.e. they may take
>>>> forever to complete. E.g. recv depends on the other end to send something,
>>>> that not necessarily will ever happen.
>>>
>>> To elaborate a bit, one example of how it's used: because unbounded may
>>> stay for long, it always spawns a new worker thread for each of them.
>>>
>>> If app submits SQEs as below, and send's are not actually sent for execution
>>> but stashed somewhere internally in a list, e.g. waiting for a worker thread
>>> to get free, it would just hang from the userspace perspective.
>>>
>>> recv(fd1), recv(fd1), send(fd1), send(fd1)
>>>
>> Hi Pavel, thank you for the patient explanation, I got the meaning of
>>   bound/unbond now, but it seems there is no difference handling bounded and unbounded work in the current code?
> 
> It was used in io-wq, so see in io-wq.[c,h] files. Not sure about 5.12+, but
> a quick look shows:
> 
> wqe->acct[IO_WQ_ACCT_BOUND].max_workers = bounded;
> ...
> wqe->acct[IO_WQ_ACCT_UNBOUND].max_workers =
> 			task_rlimit(current, RLIMIT_NPROC);
> 
Thanks, Pavel.:)
> 
> 
>>>>>> diff --git a/fs/io_uring.c b/fs/io_uring.c
>>>>>> index 6d7a1b69712b..a16b7df934d1 100644
>>>>>> --- a/fs/io_uring.c
>>>>>> +++ b/fs/io_uring.c
>>>>>> @@ -1213,7 +1213,7 @@ static void io_prep_async_work(struct io_kiocb *req)
>>>>>>         if (req->flags & REQ_F_ISREG) {
>>>>>>             if (def->hash_reg_file || (ctx->flags & IORING_SETUP_IOPOLL))
>>>>>>                 io_wq_hash_work(&req->work, file_inode(req->file));
>>>>>> -    } else {
>>>>>> +    } else if (!req->file || !S_ISBLK(file_inode(req->file)->i_mode)) {
>>>>>>             if (def->unbound_nonreg_file)
>>>>>>                 req->work.flags |= IO_WQ_WORK_UNBOUND;
>>>>>>         }
>>>
>>
> 


      reply	other threads:[~2021-04-05 16:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 14:57 [PATCH] io_uring: don't mark S_ISBLK async work as unbounded Jens Axboe
2021-04-02  8:52 ` Hao Xu
2021-04-02 10:32   ` Pavel Begunkov
2021-04-02 10:48     ` Pavel Begunkov
2021-04-04 10:57       ` Hao Xu
2021-04-04 11:02         ` Pavel Begunkov
2021-04-05 16:13           ` Hao Xu [this message]

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=8311f0ba-4bc8-3778-ace0-99d518d59d45@linux.alibaba.com \
    [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