From: "Zach O'Keefe" <zokeefe@google.com>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Saurabh Singh Sengar <ssengar@microsoft.com>,
Yang Shi <shy828301@gmail.com>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v4] mm/thp: fix "mm: thp: kill __transhuge_page_enabled()"
Date: Mon, 9 Oct 2023 06:23:09 -0700 [thread overview]
Message-ID: <CAAa6QmRcqmw1_UL--mj2HC-GxvJG1NibVi=03+ahri_DzEp5Mw@mail.gmail.com> (raw)
In-Reply-To: <22ff3362-83fc-46c6-9412-15ca36c51d54@arm.com>
On Fri, Oct 6, 2023 at 2:28 PM Ryan Roberts <ryan.roberts@arm.com> wrote:
>
> On 06/10/2023 20:11, Andrew Morton wrote:
> > On Fri, 6 Oct 2023 20:52:30 +0200 David Hildenbrand <david@redhat.com> wrote:
> >
> >>> And as I don't know what is the urgency of this patch ("mm/thp: fix
> >>> "mm: thp: kill __transhuge_page_enabled()"), I'm unable to decide which
> >>> patch needs to come first (thus requiring rework of the other patch).
> >>>
> >>> Please discuss!
> >>
> >> IMHO clearly this one.
> >
> > OK. I'll drop the "variable-order, large folios for anonymous memory" v6
> > series for now.
>
> Yep, agreed!
Thank all and sorry for the late response ; have been buried as of late.
Best,
Zach
next prev parent reply other threads:[~2023-10-09 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 20:01 Zach O'Keefe
2023-09-26 21:39 ` Yang Shi
2023-10-06 17:50 ` Andrew Morton
2023-10-09 13:22 ` Zach O'Keefe
2023-10-06 17:58 ` Andrew Morton
2023-10-06 18:52 ` David Hildenbrand
2023-10-06 19:11 ` Andrew Morton
2023-10-06 21:28 ` Ryan Roberts
2023-10-09 13:23 ` Zach O'Keefe [this message]
2023-10-06 18:53 ` David Hildenbrand
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='CAAa6QmRcqmw1_UL--mj2HC-GxvJG1NibVi=03+ahri_DzEp5Mw@mail.gmail.com' \
--to=zokeefe@google.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=ssengar@microsoft.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