linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Gavin Shan <gshan@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, djwong@kernel.org,
	willy@infradead.org, hughd@google.com,
	torvalds@linux-foundation.org, zhenyzha@redhat.com,
	shan.gavin@gmail.com
Subject: Re: [PATCH 0/4] mm/filemap: Limit page cache size to that supported by xarray
Date: Wed, 26 Jun 2024 13:38:21 -0700	[thread overview]
Message-ID: <20240626133821.b2bba4fd46278fe1e4903052@linux-foundation.org> (raw)
In-Reply-To: <4b05bdae-22e8-4906-b255-5edd381b3d21@redhat.com>

On Wed, 26 Jun 2024 10:37:00 +1000 Gavin Shan <gshan@redhat.com> wrote:

> 
> I rechecked the history, it's a bit hard to have precise fix tag for PATCH[4].
> Please let me know if you have a better one for PATCH[4].
> 
> #4
>    Fixes: 800d8c63b2e9 ("shmem: add huge pages support")
>    Cc: stable@kernel.org # v4.10+
>    Fixes: 552446a41661 ("shmem: Convert shmem_add_to_page_cache to XArray")
>    Cc: stable@kernel.org # v4.20+
> #3
>    Fixes: 793917d997df ("mm/readahead: Add large folio readahead")
>    Cc: stable@kernel.org # v5.18+
> #2
>    Fixes: 4687fdbb805a ("mm/filemap: Support VM_HUGEPAGE for file mappings")
>    Cc: stable@kernel.org # v5.18+
> #1
>    Fixes: 793917d997df ("mm/readahead: Add large folio readahead")
>    Cc: stable@kernel.org # v5.18+
> 
> I probably need to move PATCH[3] before PATCH[2] since PATCH[1] and PATCH[2]
> point to same commit.

OK, thanks.

I assume you'll be sending a new revision of the series.  And Ryan had
comments.  Please incorporate the above into the updated changelogs as
best you can.



  reply	other threads:[~2024-06-26 20:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25  9:06 Gavin Shan
2024-06-25  9:06 ` [PATCH 1/4] mm/filemap: Make MAX_PAGECACHE_ORDER acceptable to xarray Gavin Shan
2024-06-25 18:43   ` David Hildenbrand
2024-06-25  9:06 ` [PATCH 2/4] mm/filemap: Skip to allocate PMD-sized folios if needed Gavin Shan
2024-06-25 18:44   ` David Hildenbrand
2024-06-25  9:06 ` [PATCH 3/4] mm/readahead: Limit page cache size in page_cache_ra_order() Gavin Shan
2024-06-25 18:45   ` David Hildenbrand
2024-06-26  0:48     ` Gavin Shan
2024-06-25  9:06 ` [PATCH 4/4] mm/shmem: Disable PMD-sized page cache if needed Gavin Shan
2024-06-25 18:50   ` David Hildenbrand
2024-06-26  8:24     ` Ryan Roberts
2024-06-25 18:37 ` [PATCH 0/4] mm/filemap: Limit page cache size to that supported by xarray Andrew Morton
2024-06-25 18:51   ` David Hildenbrand
2024-06-25 18:58     ` Andrew Morton
2024-06-25 19:05       ` David Hildenbrand
2024-06-26  0:37         ` Gavin Shan
2024-06-26 20:38           ` Andrew Morton [this message]
2024-06-26 23:05             ` Gavin Shan
2024-06-26 20:54           ` Matthew Wilcox
2024-06-26 23:48             ` Gavin Shan

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=20240626133821.b2bba4fd46278fe1e4903052@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=djwong@kernel.org \
    --cc=gshan@redhat.com \
    --cc=hughd@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shan.gavin@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.org \
    --cc=zhenyzha@redhat.com \
    /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