From: David Hildenbrand <david@redhat.com>
To: Yang Shi <shy828301@gmail.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] mm: thp: don't have to lock page anymore when splitting PMD
Date: Fri, 4 Mar 2022 19:50:08 +0100 [thread overview]
Message-ID: <13ad4ba1-2a88-9459-3995-70af36aba33e@redhat.com> (raw)
In-Reply-To: <CAHbLzkriyBy2HqjssurLSnhoyuUzpJRZjMPNx34MTgxeO0dddg@mail.gmail.com>
On 04.03.22 19:30, Yang Shi wrote:
> On Thu, Mar 3, 2022 at 9:06 PM David Hildenbrand <david@redhat.com> wrote:
>>
>> Hi,
>>
>> This probably bounces on the list due to html junk from the gmail app.
>>
>> What happened to
>>
>> https://lore.kernel.org/linux-mm/20220131162940.210846-10-david@redhat.com/
>>
>> Included in the very series mentioned below?
>>
>> Was this silently dropped due to folio conversion collisions? :/
>
> I really didn't notice you already proposed this. Maybe folio
> conversion, maybe mlock cleanup, I can't tell. But anyway this patch
> needs to get rebased. I will submit v2 to solve the comment, will add
> your signed-off-by.
>
Why a rebase? The folio change comes via another tree (unfortunately not
Andrews tree, I wish we would have a single MM tree for MM patches).
@Andrew, the last mail I received was
+ mm-huge_memory-remove-stale-locking-logic-from-__split_huge_pmd.patch
added to -mm tree
The patch shows up in mmotm as
#[merged]mm-huge_memory-remove-stale-locking-logic-from-__split_huge_pmd.patch
... which shouldn't be true.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-03-04 18:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 22:20 [PATCH] mm: thp: don't have to lock page anymore when splitting PMD Yang Shi
2022-03-04 2:25 ` Miaohe Lin
2022-03-04 3:12 ` Yang Shi
[not found] ` <CADFyXm6W9CVkO4XPYep-tHg55c8m8NES783kcVYrdjSMbzYoDA@mail.gmail.com>
2022-03-04 18:30 ` Yang Shi
2022-03-04 18:50 ` David Hildenbrand [this message]
2022-03-04 19:01 ` Yang Shi
2022-03-07 2:07 ` Andrew Morton
2022-03-07 8:24 ` David Hildenbrand
2022-03-07 23:43 ` Andrew Morton
2022-03-08 0:03 ` Yang Shi
2022-03-08 0:50 ` Andrew Morton
2022-03-08 0:59 ` Yang Shi
2022-03-08 2:36 ` Hugh Dickins
2022-03-08 3:12 ` Yang Shi
2022-03-08 8: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=13ad4ba1-2a88-9459-3995-70af36aba33e@redhat.com \
--to=david@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.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;
as well as URLs for NNTP newsgroup(s).