From: Gavin Shan <gshan@redhat.com>
To: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: 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 10:37:00 +1000 [thread overview]
Message-ID: <4b05bdae-22e8-4906-b255-5edd381b3d21@redhat.com> (raw)
In-Reply-To: <f27d4fa3-0b0f-4646-b6c3-45874f005b46@redhat.com>
On 6/26/24 5:05 AM, David Hildenbrand wrote:
> On 25.06.24 20:58, Andrew Morton wrote:
>> On Tue, 25 Jun 2024 20:51:13 +0200 David Hildenbrand <david@redhat.com> wrote:
>>
>>>> I could split them and feed 1&2 into 6.10-rcX and 3&4 into 6.11-rc1. A
>>>> problem with this approach is that we're putting a basically untested
>>>> combination into -stable: 1&2 might have bugs which were accidentally
>>>> fixed in 3&4. A way to avoid this is to add cc:stable to all four
>>>> patches.
>>>>
>>>> What are your thoughts on this matter?
>>>
>>> Especially 4 should also be CC stable, so likely we should just do it
>>> for all of them.
>>
>> Fine. A Fixes: for 3 & 4 would be good. Otherwise we're potentially
>> asking for those to be backported further than 1 & 2, which seems
>> wrong.
>
> 4 is shmem fix, which likely dates back a bit longer.
>
>>
>> Then again, by having different Fixes: in the various patches we're
>> suggesting that people split the patch series apart as they slot things
>> into the indicated places. In other words, it's not a patch series at
>> all - it's a sprinkle of independent fixes. Are we OK thinking of it
>> in that fashion?
>
> The common themes is "pagecache cannot handle > order-11", #1-3 tackle "ordinary" file THP, #4 tackles shmem THP.
>
> So I'm not sure we should be splitting it apart. It's just that shmem THP arrived before file THP :)
>
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.
Thanks,
Gavin
next prev parent reply other threads:[~2024-06-26 0:37 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 [this message]
2024-06-26 20:38 ` Andrew Morton
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=4b05bdae-22e8-4906-b255-5edd381b3d21@redhat.com \
--to=gshan@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=djwong@kernel.org \
--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