From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yang Shi <shy828301@gmail.com>,
David Hildenbrand <david@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
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>,
Naresh Kamboju <naresh.kamboju@linaro.org>
Subject: Re: [PATCH] mm: thp: don't have to lock page anymore when splitting PMD
Date: Mon, 7 Mar 2022 18:36:42 -0800 (PST) [thread overview]
Message-ID: <8f419d19-c83d-bbcd-8936-2d64ced7464c@google.com> (raw)
In-Reply-To: <20220307165015.77fbcbe9e1fa2fe15f3eb239@linux-foundation.org>
On Mon, 7 Mar 2022, Andrew Morton wrote:
>
> OK, looks sane. Can someone please test all this?
Only the briefest of testing, but
mmotm 2022-03-06-20-33
minus mm-thp-dont-have-to-lock-page-anymore-when-splitting-pmd.patch
plus mm-huge_memory-remove-stale-locking-logic-from-__split_huge_pmd.patch
plus mm-huge_memory-remove-stale-locking-logic-from-__split_huge_pmd-fix.patch
is infinitely better than mmotm 2022-03-06-20-33.
I could just about reach a login on yesterday's mmotm, but graphics no.
Couldn't spend time to investigate, but Naresh's mail today that LTP
thp04 timeouted (hey, I'm English, we say timed out!) inspired me to
try booting with transparent_hugepage=never on cmdline, and that worked.
Again, no time to investigate, but the combination above has booted
and is running load, including transparent hugepages. And before
setting that load going, I did try LTP thp04, which passed.
(There is an unrelated console printk lockdep spew, and am I the only
one to see these mm/workingset.c:567 shadow_lru_isolate warnings that
started up a week or three ago?)
Must dash,
Hugh
next prev parent reply other threads:[~2022-03-08 2:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 22:20 Yang Shi
2022-03-04 2:25 ` Miaohe Lin
2022-03-04 3:12 ` Yang Shi
2022-03-04 5:06 ` David Hildenbrand
2022-03-04 18:30 ` Yang Shi
2022-03-04 18:50 ` David Hildenbrand
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 [this message]
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=8f419d19-c83d-bbcd-8936-2d64ced7464c@google.com \
--to=hughd@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naresh.kamboju@linaro.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