public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jeff Moyer <[email protected]>
To: Jens Axboe <[email protected]>
Cc: io-uring <[email protected]>
Subject: Re: [PATCH] io_uring: don't allow IORING_SETUP_NO_MMAP rings on highmem pages
Date: Tue, 03 Oct 2023 14:24:22 -0400	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]> (Jens Axboe's message of "Tue, 3 Oct 2023 10:27:29 -0600")

Jens Axboe <[email protected]> writes:

> On 10/3/23 10:30 AM, Jeff Moyer wrote:
>> Hi, Jens,
>> 
[snip]
>> What do you think about throwing a printk_once in there that explains
>> the problem?  I'm worried that this will fail somewhat randomly, and it
>> may not be apparent to the user why.  We should also add documentation,
>> of course, and encourage developers to add fallbacks for this case.
>
> For both cases posted, it's rather more advanced use cases. And 32-bit
> isn't so prevalent anymore, thankfully. I was going to add to the man
> pages explaining this failure case. Not sure it's worth adding a printk
> for though.

I try not to make decisions based on how prevalent I think a particular
configuration is (mainly because I'm usually wrong).  Anyway, it's not a
big deal, I'm glad you gave it some thought.

> FWIW, once I got an arm32 vm setup, it fails everytime for me. Not sure
> how it'd do on 32-bit x86, similarly or more randomly. But yeah it's
> definitely at the mercy of how things are mapped.

...and potentially the load on the system.  Anyway, it's fine with me to
keep it as is.  We can always add a warning later if it ends up being a
problem.

Thanks!
Jeff


  reply	other threads:[~2023-10-03 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 16:02 [PATCH] io_uring: don't allow IORING_SETUP_NO_MMAP rings on highmem pages Jens Axboe
2023-10-03 16:30 ` Jeff Moyer
2023-10-03 16:27   ` Jens Axboe
2023-10-03 18:24     ` Jeff Moyer [this message]
2023-10-03 18:25       ` 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