The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: William Kucharski <william.kucharski@linux.dev>
To: Usama Arif <usama.arif@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	jack@suse.cz, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	willy@infradead.org, david@kernel.org, hannes@cmpxchg.org,
	kas@kernel.org, shakeel.butt@linux.dev, kernel-team@meta.com
Subject: Re: [PATCH] mm: make mmap_miss accounting symmetric for VM_SEQ_READ
Date: Tue, 26 May 2026 03:30:55 -0600	[thread overview]
Message-ID: <715DF460-33D0-441C-A732-D029EBAE4BBF@linux.dev> (raw)
In-Reply-To: <20260525145751.2671248-1-usama.arif@linux.dev>

Looks good to me.

Reviewed-by: William Kucharski <william.kucharski@linux.dev>

> On May 25, 2026, at 08:57, Usama Arif <usama.arif@linux.dev> wrote:
> 
> do_sync_mmap_readahead() skips both the mmap_miss increment and the
> MMAP_LOTSAMISS check for VM_SEQ_READ mappings, since sequential access
> is non-speculative and should always read ahead. The two decrement
> sites in do_async_mmap_readahead() and filemap_map_pages() do not
> mirror this skip, so concurrent faults on a VM_SEQ_READ mapping can
> still drive ra->mmap_miss down to zero through the decrement paths
> even though nothing in the sync path ever increments it. The counter
> itself is per-file (file->f_ra.mmap_miss), so it can be moved by any
> VMA mapping the file, not just the one currently faulting.
> 
> Skip the decrement for VM_SEQ_READ in both decrement sites so the
> counter only moves for mappings that also participate in the
> increment side. No functional change for VM_SEQ_READ users, since the
> increment-side gate already prevents the counter from being consulted
> on their behalf, but it stops a VM_SEQ_READ mapping from biasing the
> counter for other mappings of the same file.
> 
> Signed-off-by: Usama Arif <usama.arif@linux.dev>
> ---
> mm/filemap.c | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
> 
> diff --git a/mm/filemap.c b/mm/filemap.c
> index 5aaba0d3e81d..cca20e350c95 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -3433,8 +3433,13 @@ static struct file *do_async_mmap_readahead(struct vm_fault *vmf,
> * Don't touch the mmap_miss counter to avoid decreasing it multiple
> * times for a single folio and break the balance with mmap_miss
> * increase in do_sync_mmap_readahead().
> + *
> + * VM_SEQ_READ mappings skip the mmap_miss increment in
> + * do_sync_mmap_readahead(), so skip the decrement here as well to
> + * keep the counter symmetric.
> */
> - if (likely(!folio_test_locked(folio))) {
> + if (likely(!folio_test_locked(folio)) &&
> +    !(vmf->vma->vm_flags & VM_SEQ_READ)) {
> mmap_miss = READ_ONCE(ra->mmap_miss);
> if (mmap_miss)
> WRITE_ONCE(ra->mmap_miss, --mmap_miss);
> @@ -3935,10 +3940,15 @@ vm_fault_t filemap_map_pages(struct vm_fault *vmf,
> * In such situation, read-ahead is only a waste of IO.
> * Don't decrease mmap_miss in this scenario to make sure
> * we can stop read-ahead.
> + *
> + * VM_SEQ_READ mappings skip the mmap_miss increment in
> + * do_sync_mmap_readahead(), so skip the decrement here as
> + * well to keep the counter symmetric.
> */
> if ((map_ret & VM_FAULT_NOPAGE) &&
>    !(vmf->flags & FAULT_FLAG_TRIED) &&
> -    !folio_test_workingset(folio)) {
> +    !folio_test_workingset(folio) &&
> +    !(vma->vm_flags & VM_SEQ_READ)) {
> unsigned short mmap_miss;
> 
> mmap_miss = READ_ONCE(file->f_ra.mmap_miss);
> -- 
> 2.52.0
> 
> 


  parent reply	other threads:[~2026-05-26  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 14:57 [PATCH] mm: make mmap_miss accounting symmetric for VM_SEQ_READ Usama Arif
2026-05-25 15:03 ` Usama Arif
2026-05-26  9:30 ` William Kucharski [this message]
2026-06-02 11:14 ` Jan Kara

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=715DF460-33D0-441C-A732-D029EBAE4BBF@linux.dev \
    --to=william.kucharski@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=jack@suse.cz \
    --cc=kas@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shakeel.butt@linux.dev \
    --cc=usama.arif@linux.dev \
    --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