public inbox for [email protected]
 help / color / mirror / Atom feed
From: Justin Forbes <[email protected]>
To: Jens Axboe <[email protected]>
Cc: [email protected], [email protected],
	Linux Kernel Mailing List <[email protected]>
Subject: Re: [PATCH] io_uring: Remove CONFIG_EXPERT
Date: Thu, 27 May 2021 09:12:01 -0500	[thread overview]
Message-ID: <CAFbkSA1G2ajKQg4eA947dv0Pcmyf-JQbkn8-jYnmUeMAEpfHtw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

On Thu, May 27, 2021 at 8:43 AM Jens Axboe <[email protected]> wrote:
>
> On 5/26/21 4:34 PM, Justin M. Forbes wrote:
> > While IO_URING has been in fairly heavy development, it is hidden behind
> > CONFIG_EXPERT with a default of on.  It has been long enough now that I
> > think we should remove EXPERT and allow users and distros to decide how
> > they want this config option set without jumping through hoops.
>
> The whole point of EXPERT is to ensure that it doesn't get turned off
> "by accident". It's a core feature, and something that more and more
> apps or libraries are relying on. It's not something I intended to ever
> go away, just like it would never go away for eg futex or epoll support.
>

I am not arguing with that, I don't expect it will go away. I
certainly do not have an issue with it defaulting to on, and I didn't
even submit this with intention to turn it off for default Fedora. I
do think that there are cases where people might not wish it turned on
at this point in time. Hiding it behind EXPERT makes it much more
difficult than it needs to be.  There are plenty of config options
that are largely expected default and not hidden behind EXPERT.

Justin


  reply	other threads:[~2021-05-27 14:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 22:34 [PATCH] io_uring: Remove CONFIG_EXPERT Justin M. Forbes
2021-05-26 22:55 ` Pavel Begunkov
2021-05-27 13:43 ` Jens Axboe
2021-05-27 14:12   ` Justin Forbes [this message]
2021-05-27 14:19     ` Jens Axboe
2021-05-27 16:01       ` Justin Forbes
2021-05-28  7:59         ` David Laight
2021-06-03 15:43         ` Justin Forbes
2021-06-03 15:46           ` 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 \
    --in-reply-to=CAFbkSA1G2ajKQg4eA947dv0Pcmyf-JQbkn8-jYnmUeMAEpfHtw@mail.gmail.com \
    [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