From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New global USE flag: io-uring
Date: Thu, 12 Dec 2024 18:19:12 +0100 [thread overview]
Message-ID: <32aea319-e33a-4b68-813c-223da445e60a@gentoo.org> (raw)
In-Reply-To: <VfAkSpK_AjO5266_d85GO7TcwH6VCJMISOguwDg9kRwbvbjkM9YqOqcIsaKYozvjcyQmjv8id4ExBpR2DWT3Hkhw0puC_Zumj9QRw8sZBV4=@pm.me>
[-- Attachment #1.1.1: Type: text/plain, Size: 1062 bytes --]
On 08/11/2024 18.20, Filip Kobierski wrote:
> Hello everyone,
>
> lately I have been looking into the io_uring functionality in the
> kernel and apps that I use -- what could be a non-generic USE flag
> shared by mpd and qemu?
>
> I have noticed that currently 9 packages[1] have an io-uring USE
> flag. All of them use it for enabling the use of io_uring
> system calls.
>
> The feature was introduced in 5.1 and the oldest we ship is 5.10
> so I think there will be no compatibility issues.
>
> Introducing a new io-uring global USE flag would encourage users
> to enable it globally and simplify the configuration.
>
> The USE description that I propose is
> "Enable the use of io_uring system calls for efficient async IO".
> Of course if there is something more fitting it should be chosen,
> I have no hard opinions here.
>
> What do you think about it?
I also think io-uring is a good candidate for a global use flag. Given
that there where no objections, please feel encouraged to propose a
tree-wide patch.
- Flow
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 21567 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
prev parent reply other threads:[~2024-12-12 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 17:20 [gentoo-dev] [RFC] New global USE flag: io-uring Filip Kobierski
2024-11-15 9:08 ` Jaco Kroon
2024-12-12 17:19 ` Florian Schmaus [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=32aea319-e33a-4b68-813c-223da445e60a@gentoo.org \
--to=flow@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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