From: David Rientjes <rientjes@google.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Hui Zhu <teawater@gmail.com>,
hannes@cmpxchg.org, mhocko@kernel.org, vdavydov.dev@gmail.com,
akpm@linux-foundation.org, hughd@google.com,
yang.shi@linux.alibaba.com, dan.j.williams@intel.com,
aneesh.kumar@linux.ibm.com, sean.j.christopherson@intel.com,
thellstrom@vmware.com, guro@fb.com, shakeelb@google.com,
chris@chrisdown.name, tj@kernel.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-mm@kvack.org, Hui Zhu <teawaterz@linux.alibaba.com>
Subject: Re: [PATCH] mm, memcg: Add memory.transparent_hugepage_disabled
Date: Tue, 24 Mar 2020 12:17:11 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2003241215580.34058@chino.kir.corp.google.com> (raw)
In-Reply-To: <20200324121758.paxxthsi2f4hngfa@box>
On Tue, 24 Mar 2020, Kirill A. Shutemov wrote:
> On Tue, Mar 24, 2020 at 06:31:56PM +0800, Hui Zhu wrote:
> > /sys/kernel/mm/transparent_hugepage/enabled is the only interface to
> > control if the application can use THP in system level.
>
> No. We have prctl(PR_SET_THP_DISABLE) too.
>
Yeah, I think this is the key point since this can be inherited across
fork and thus you already have the ability to disable thp for a process
where you cannot even modify the binary to do MADV_NOHUGEPAGE.
next prev parent reply other threads:[~2020-03-24 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 10:31 [PATCH] mm, memcg: Add memory.transparent_hugepage_disabled Hui Zhu
2020-03-24 11:00 ` Michal Hocko
2020-03-24 12:30 ` teawater
2020-03-24 13:17 ` Michal Hocko
2020-03-24 12:17 ` Kirill A. Shutemov
2020-03-24 19:17 ` David Rientjes [this message]
2020-03-24 13:23 ` Chris Down
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=alpine.DEB.2.21.2003241215580.34058@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=cgroups@vger.kernel.org \
--cc=chris@chrisdown.name \
--cc=dan.j.williams@intel.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=shakeelb@google.com \
--cc=teawater@gmail.com \
--cc=teawaterz@linux.alibaba.com \
--cc=tglx@linutronix.de \
--cc=thellstrom@vmware.com \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.com \
--cc=yang.shi@linux.alibaba.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).