public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Hao Xu <[email protected]>
Cc: Jens Axboe <[email protected]>,
	[email protected], Joseph Qi <[email protected]>,
	Pavel Begunkov <[email protected]>
Subject: Re: [PATCH v2] io_uring: split logic of force_nonblock
Date: Tue, 19 Oct 2021 18:23:11 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Mon, 18 Oct 2021 21:34:31 +0800, Hao Xu wrote:
> Currently force_nonblock stands for three meanings:
>  - nowait or not
>  - in an io-worker or not(hold uring_lock or not)
> 
> Let's split the logic to two flags, IO_URING_F_NONBLOCK and
> IO_URING_F_UNLOCKED for convenience of the next patch.
> 
> [...]

Applied, thanks!

[1/1] io_uring: split logic of force_nonblock
      commit: 3b44b3712c5b19b0af11c25cd978abdc3680d5e7

Best regards,
-- 
Jens Axboe



      parent reply	other threads:[~2021-10-20  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 13:34 [PATCH v2] io_uring: split logic of force_nonblock Hao Xu
2021-10-19 23:49 ` Pavel Begunkov
2021-10-20  0:23 ` Jens Axboe [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=163468938922.717790.14117389631747248538.b4-ty@kernel.dk \
    [email protected] \
    [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