public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCH v2] Add option to ignore O_NONBLOCK for retry purposes
Date: Fri, 18 Jun 2021 16:10:39 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi,

After thinking a bit more about this, I think this makes more sense to
do as a setup flag. That means that libraries/applications using it
can have this just in their setup path instead of the hot path, and
it also means that we can save precious space in the sqe flags.

Hence v2 turns this from an sqe flag into a setup flag instead, and
makes the behavior per ring rather than per sqe.

-- 
Jens Axboe



             reply	other threads:[~2021-06-18 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 22:10 Jens Axboe [this message]
2021-06-18 22:10 ` [PATCH] io_uring: add IORING_SETUP_IGNORE_ONONBLOCK flag 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