From: Andrew Morton <akpm@linux-foundation.org>
To: Sidhartha Kumar <sidhartha.kumar@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
willy@infradead.org, songmuchun@bytedance.com,
mike.kravetz@oracle.com, david@redhat.com
Subject: Re: [PATCH v2 1/1] mm/filemap: remove hugetlb special casing in filemap.c
Date: Tue, 11 Jul 2023 12:32:45 -0700 [thread overview]
Message-ID: <20230711123245.473400853fd1227459017650@linux-foundation.org> (raw)
In-Reply-To: <20230710230450.110064-2-sidhartha.kumar@oracle.com>
On Mon, 10 Jul 2023 16:04:50 -0700 Sidhartha Kumar <sidhartha.kumar@oracle.com> wrote:
> Remove special cased hugetlb handling code within the page cache by
> changing the granularity of each index to the base page size rather than
> the huge page size. Adds new wrappers for hugetlb code to to interact with the
> page cache which convert to a linear index.
folio_more_pages() was just removed by "filemap: add
filemap_map_folio_range()"
(https://lkml.kernel.org/r/20230710204339.3554919-35-willy@infradead.org).
It looks like simply dropping that hunk is OK, but please check.
I'll be pushing this all out in a couple hours I expect.
However the series which contains "filemap: add
filemap_map_folio_range()" might be about to be dropped because of
possible s390 breakage.
Also, I don't think it's necessary to have a [0/N] intro for a single
patch. Maybe crunch all the (useful) info into the single patch's
changelog?
Thanks.
next prev parent reply other threads:[~2023-07-11 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 23:04 [PATCH v2 0/1] change ->index to PAGE_SIZE for hugetlb pages Sidhartha Kumar
2023-07-10 23:04 ` [PATCH v2 1/1] mm/filemap: remove hugetlb special casing in filemap.c Sidhartha Kumar
2023-07-11 19:32 ` Andrew Morton [this message]
2023-07-21 20:22 ` Mike Kravetz
2023-07-20 0:00 ` [PATCH v2 0/1] change ->index to PAGE_SIZE for hugetlb pages Mike Kravetz
2023-07-22 4:05 ` Matthew Wilcox
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=20230711123245.473400853fd1227459017650@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=sidhartha.kumar@oracle.com \
--cc=songmuchun@bytedance.com \
--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