From: Michal Hocko <mhocko@suse.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: Eiichi Tsukata <eiichi.tsukata@nutanix.com>,
corbet@lwn.net, mcgrof@kernel.org, keescook@chromium.org,
yzaikin@google.com, akpm@linux-foundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
felipe.franciosi@nutanix.com
Subject: Re: [RFC PATCH] mm, oom: introduce vm.sacrifice_hugepage_on_oom
Date: Wed, 17 Feb 2021 08:57:09 +0100 [thread overview]
Message-ID: <YCzMVa5QSyUtlmnI@dhcp22.suse.cz> (raw)
In-Reply-To: <bb3508e7-48d1-fa1b-f1a0-7f42be55ed9c@oracle.com>
On Tue 16-02-21 14:30:15, Mike Kravetz wrote:
[...]
> However, this is an 'opt in' feature. So, I would not expect anyone who
> carefully plans the size of their hugetlb pool to enable such a feature.
> If there is a use case where hugetlb pages are used in a non-essential
> application, this might be of use.
I would really like to hear about the specific usecase. Because it
smells more like a misconfiguration. What would be non-essential hugetlb
pages? This is not a resource to be pre-allocated just in case, right?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-02-17 7:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 3:07 [RFC PATCH] mm, oom: introduce vm.sacrifice_hugepage_on_oom Eiichi Tsukata
2021-02-16 8:12 ` Michal Hocko
2021-02-16 21:53 ` David Rientjes
2021-02-17 7:54 ` Michal Hocko
2021-02-17 14:59 ` Shakeel Butt
2021-02-16 22:30 ` Mike Kravetz
2021-02-17 7:57 ` Michal Hocko [this message]
2021-02-17 10:42 ` Eiichi Tsukata
2021-02-17 12:31 ` Michal Hocko
2021-02-17 12:40 ` Michal Hocko
2021-02-18 12:22 ` Eiichi Tsukata
2021-02-18 12:39 ` Chris Down
2021-02-16 13:38 ` Chris Down
2021-02-17 9:09 ` 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=YCzMVa5QSyUtlmnI@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=eiichi.tsukata@nutanix.com \
--cc=felipe.franciosi@nutanix.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=yzaikin@google.com \
/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).