public inbox for [email protected]
 help / color / mirror / Atom feed
From: "Drew DeVault" <[email protected]>
To: "Pavel Begunkov" <[email protected]>, <[email protected]>
Subject: Re: Polling on an io_uring file descriptor
Date: Fri, 22 Oct 2021 12:26:17 +0200	[thread overview]
Message-ID: <CF5V3TYHMZVC.M9GAOFXLMI4T@taiga> (raw)
In-Reply-To: <[email protected]>

On Fri Oct 22, 2021 at 11:49 AM CEST, Pavel Begunkov wrote:
> It's potentially problematic, even now we have a couple of other
> spots relying on it. Is there a good reason why it's needed?

Yes, I have an application which uses one io_uring to manage a second
io_uring. I can skip registering the fd (current approach) or I can use
a different mechanism for managing the second uring (e.g. poll), but it
seems awkward and poorly justified that this invariant would exist.

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20  9:21 Polling on an io_uring file descriptor Drew DeVault
2021-10-20 10:02 ` Drew DeVault
2021-10-20 10:15 ` Pavel Begunkov
2021-10-20 11:44   ` Drew DeVault
2021-10-20 11:58     ` Pavel Begunkov
2021-10-20 12:00       ` Drew DeVault
2021-10-22  7:59         ` Drew DeVault
2021-10-22  9:49           ` Pavel Begunkov
2021-10-22 10:26             ` Drew DeVault [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=CF5V3TYHMZVC.M9GAOFXLMI4T@taiga \
    [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