From: Mike Kravetz <mike.kravetz@oracle.com>
To: Michal Hocko <mhocko@suse.com>, akpm@linux-foundation.org
Cc: almasrymina@google.com, anshuman.khandual@arm.com,
bodeddub@amazon.com, bp@alien8.de, bsingharora@gmail.com,
chenhuang5@huawei.com, corbet@lwn.net,
dave.hansen@linux.intel.com, david@redhat.com, hpa@zytor.com,
joao.m.martins@oracle.com, jroedel@suse.de, linmiaohe@huawei.com,
luto@kernel.org, mchehab+huawei@kernel.org, mingo@redhat.com,
mm-commits@vger.kernel.org, naoya.horiguchi@nec.com,
oneukum@suse.com, osalvador@suse.de, paulmck@kernel.org,
pawan.kumar.gupta@linux.intel.com, peterz@infradead.org,
rdunlap@infradead.org, rientjes@google.com,
song.bao.hua@hisilicon.com, songmuchun@bytedance.com,
tglx@linutronix.de, viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: + mm-hugetlb-alloc-the-vmemmap-pages-associated-with-each-hugetlb-page.patch added to -mm tree
Date: Tue, 16 Mar 2021 09:54:49 -0700 [thread overview]
Message-ID: <f9901048-4ee1-85af-82f4-e3c2c71309bc@oracle.com> (raw)
In-Reply-To: <YFCHbGtshunwQxyc@dhcp22.suse.cz>
On 3/16/21 3:24 AM, Michal Hocko wrote:
> Andrew,
> this patchset is still not ready for mmotm. Hugetlb freeing path needs a
> major surgery because it can be called from atomic contexts and a simple
> fix http://lkml.kernel.org/r/20210311021321.127500-1-mike.kravetz@oracle.com
> has been nacked by Peter. Until this is handled properly this has to
> wait and build on top.
>
Unfortunately, I tend to agree.
Technically, this patchset does not add anything 'new' WRT challenges
with the put_page path. It will add a new condition where that path
could sleep. However, handling the possibility is an issue with the
existing code. What this patchset does add is additional complexity
to the existing code paths. It would be better to wait for modifications
that take into account put_page/free_huge_page can be called from any
context.
I am working on such changes and it is a priority. However, this is
going to require quite a bit of code change.
--
Mike Kravetz
next prev parent reply other threads:[~2021-03-16 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 20:48 + mm-hugetlb-alloc-the-vmemmap-pages-associated-with-each-hugetlb-page.patch added to -mm tree akpm
2021-03-16 10:24 ` Michal Hocko
2021-03-16 16:54 ` Mike Kravetz [this message]
2021-03-18 7:28 ` [External] " Muchun Song
-- strict thread matches above, loose matches on Subject: below --
2021-05-10 3:54 akpm
2021-03-08 20:10 akpm
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=f9901048-4ee1-85af-82f4-e3c2c71309bc@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=anshuman.khandual@arm.com \
--cc=bodeddub@amazon.com \
--cc=bp@alien8.de \
--cc=bsingharora@gmail.com \
--cc=chenhuang5@huawei.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=hpa@zytor.com \
--cc=joao.m.martins@oracle.com \
--cc=jroedel@suse.de \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=mm-commits@vger.kernel.org \
--cc=naoya.horiguchi@nec.com \
--cc=oneukum@suse.com \
--cc=osalvador@suse.de \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=song.bao.hua@hisilicon.com \
--cc=songmuchun@bytedance.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--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