linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Yafang Shao <laoar.shao@gmail.com>,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] mm/readahead: Fix large folio support in async readahead
Date: Wed, 13 Nov 2024 09:12:08 +0100	[thread overview]
Message-ID: <70c28250-f119-435a-9cbe-778fe80beab0@redhat.com> (raw)
In-Reply-To: <ZzQo2JrXbGEkpPqb@casper.infradead.org>

On 13.11.24 05:19, Matthew Wilcox wrote:
> On Tue, Nov 12, 2024 at 04:19:07PM +0100, David Hildenbrand wrote:
>> Someone configured: "Don't readahead more than 128KiB"
> 
> Did they, though?  I have nothing but contempt for the thousands of
> parameters that we expect sysadmins to configure.  It's ridiculous and
> it needs to stop.  So, we listen to the program that has told us "We
> want 2MB pages" and not to the sysadmin who hasn't changed the value of
> readahead from one that was originally intended for floppy discs.

If something can be achieved using MADV_HUGEPAGE but not using 
auto-tuning (ordinary readahead / no MADV_HUGEPAGE) it's a warning sign 
at least to me ...

FWIW, I agree that the parameters we have are confusing. But selectively 
ignoring them ... I don't know.

If the parameter is effectively useless on some devices (except floppy 
discs?) maybe it should be set to "0=auto" (and modification attempts 
failing/being ignored) or simply ignore for all of readahead.

Anyhow, your call. I'll see if I can make sense of the code and come up 
with a comment that explains the situation.

-- 
Cheers,

David / dhildenb



      reply	other threads:[~2024-11-13  8:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 14:17 Yafang Shao
2024-11-11 10:33 ` David Hildenbrand
2024-11-11 14:28   ` Yafang Shao
2024-11-11 15:05     ` David Hildenbrand
2024-11-11 15:26       ` David Hildenbrand
2024-11-11 16:13         ` Yafang Shao
2024-11-11 16:08       ` Yafang Shao
2024-11-11 18:31         ` David Hildenbrand
2024-11-11 19:10           ` Yafang Shao
2024-11-12 15:19             ` David Hildenbrand
2024-11-13  2:16               ` Yafang Shao
2024-11-13  8:28                 ` David Hildenbrand
2024-11-13  9:46                   ` David Hildenbrand
2024-11-13  9:54                   ` Yafang Shao
2024-11-13 10:24                     ` David Hildenbrand
2024-11-13  4:19               ` Matthew Wilcox
2024-11-13  8:12                 ` David Hildenbrand [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=70c28250-f119-435a-9cbe-778fe80beab0@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=laoar.shao@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=stable@vger.kernel.org \
    --cc=willy@infradead.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