From: Hugh Dickins <hughd@google.com>
To: Vincent Donnefort <vdonnefort@google.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Andrew Bresticker <abrestic@rivosinc.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
maz@kernel.org, seanjc@google.com
Subject: Re: [PATCH v2] mm/memory: Don't require head page for do_set_pmd()
Date: Tue, 20 Aug 2024 13:33:59 -0700 (PDT) [thread overview]
Message-ID: <0d4f99bd-609a-8c76-b665-adcf942e6a74@google.com> (raw)
In-Reply-To: <ZsL_XvRL-OgEqmvv@google.com>
On Mon, 19 Aug 2024, Vincent Donnefort wrote:
> On Tue, Jun 11, 2024 at 07:22:03PM +0100, Matthew Wilcox wrote:
> > On Tue, Jun 11, 2024 at 11:06:22AM -0700, Andrew Morton wrote:
...
> > > You know what I'm going to ask ;) I'm assuming that the runtime effects
> > > are "small performance optimization" and that "should we backport the
> > > fix" is "no".
> >
> > We're going to stop using PMDs to map large folios unless the fault is
> > within the first 4KiB of the PMD. No idea how many workloads that
> > affects, but it only needs to be backported as far as v6.8, so we
> > may as well backport it.
>
> Hi, I am reviving this thread after noticing this comment attached
> to the fix.
>
> If you intend to install PTE level mappings for faults that happen outside of
> the first 4KiB, I believe this will make THP support for KVM ineffective.
You can relax, it's okay: where Matthew wrote "We're going to stop...",
he was describing the runtime effects of the bug (now fixed) to Andrew,
not proposing to make a change to mess up THP support.
The fix was backported to v6.9.N, but was too late for v6.8.N EOL.
Hugh
next prev parent reply other threads:[~2024-08-20 20:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 15:32 Andrew Bresticker
2024-06-11 15:33 ` David Hildenbrand
2024-06-11 18:06 ` Andrew Morton
2024-06-11 18:22 ` Matthew Wilcox
2024-06-11 20:07 ` Andrew Morton
2024-06-11 21:18 ` Hugh Dickins
2024-06-12 18:41 ` David Hildenbrand
2024-08-19 8:16 ` Vincent Donnefort
2024-08-20 20:33 ` Hugh Dickins [this message]
2024-06-11 18:03 ` Matthew Wilcox
2024-06-11 18:21 ` Andrew Morton
2024-06-11 18:38 ` 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=0d4f99bd-609a-8c76-b665-adcf942e6a74@google.com \
--to=hughd@google.com \
--cc=abrestic@rivosinc.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maz@kernel.org \
--cc=seanjc@google.com \
--cc=vdonnefort@google.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