From: Sidhartha Kumar <sidhartha.kumar@oracle.com>
To: Mike Kravetz <mike.kravetz@oracle.com>,
Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
songmuchun@bytedance.com
Subject: Re: [PATCH v6] mm/filemap: remove hugetlb special casing in filemap.c
Date: Fri, 18 Aug 2023 11:54:24 -0700 [thread overview]
Message-ID: <71864148-6493-30fc-ada4-6bc242b6176f@oracle.com> (raw)
In-Reply-To: <20230818183407.GA5850@monkey>
On 8/18/23 11:34 AM, Mike Kravetz wrote:
> On 08/18/23 19:09, Matthew Wilcox wrote:
>>
>> There's also a conceptual reduction in complexity. We no longer need to
>> think about whether the inode is hugetlb or not before doing the lookup
>> and scaling the byte offset differently.
>
> I 'think' this was the primary motivation for this patch.
>
> Recent discussions about HGM always came back to hugetlb special case code
> in the core mm. HGM would add a little more, and most people thought there
> was too much already. Most everyone in those discussions agreed there
> should be some effort to unify hugetlb and core mm code as much as possible
> to reduce these special cases. This is one step in that direction.
>
yes, the motivation for this patch came from the discussion about the
various places in mm where hugetlb is special cased and how there should
be an effort to unify these cases. As Matthew mentions, this series gets
rid of branches that would occur on every page cache lookup. The
comments in pagemap.h also mention
- * (TODO: remove once hugetlb pages will have ->index in PAGE_SIZE)
so this has been a goal for the page cache.
Thanks
Sidhartha Kumar
> As a hugetlb maintainer, I don't like any decrease in performance even
> if it is not readily observable. However, as a member of the mm community
> I like the fact that there is less special case hugetlb code. Overall,
> I consider this a win.
next prev parent reply other threads:[~2023-08-18 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 18:18 Sidhartha Kumar
2023-08-18 18:03 ` Andrew Morton
2023-08-18 18:09 ` Matthew Wilcox
2023-08-18 18:34 ` Mike Kravetz
2023-08-18 18:54 ` Sidhartha Kumar [this message]
2023-08-18 19:24 ` Andrew Morton
2023-08-21 18:33 ` Mike Kravetz
2023-09-05 4:05 ` Sidhartha Kumar
2023-09-07 0:18 ` Mike Kravetz
2023-08-22 17:15 ` 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=71864148-6493-30fc-ada4-6bc242b6176f@oracle.com \
--to=sidhartha.kumar@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@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