From: "Drew DeVault" <[email protected]>
To: "Drew DeVault" <[email protected]>,
"Pavel Begunkov" <[email protected]>,
<[email protected]>
Subject: Re: Polling on an io_uring file descriptor
Date: Fri, 22 Oct 2021 09:59:00 +0200 [thread overview]
Message-ID: <CF5RZ29XMY8T.2FIJ64YU0UFJ7@taiga> (raw)
In-Reply-To: <CF47UZE6WXQ6.1MZDZ8OPGM0TW@taiga>
On Wed Oct 20, 2021 at 2:00 PM CEST, Drew DeVault wrote:
> > Surely should be updated if not mentioned
>
> That, or the constraint removed? The reasoning is a bit obscure and I
> suspect that this case could be made possible.
So I dug into this a bit more, and the constraint seems to be to avoid a
reference loop when CONFIG_UNIX=n. I grepped Google and SourceGraph for
"CONFIG_UNIX=n" and only found two kernel configs with Unix sockets
disabled, neither of which had io_uring enabled. Given the rather
arbitrary restriction on registering io_urings with each other, and the
apparent absence of a use-case for io_uring without Unix sockets, can we
just require CONFIG_UNIX for io_uring and remove the limitation?
next prev parent reply other threads:[~2021-10-22 7:59 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 [this message]
2021-10-22 9:49 ` Pavel Begunkov
2021-10-22 10:26 ` Drew DeVault
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=CF5RZ29XMY8T.2FIJ64YU0UFJ7@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