linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: vijay nag <vijunag@gmail.com>
Cc: rppt@linux.ibm.com, linux-mm@kvack.org
Subject: Re: Cgroups support for THP
Date: Mon, 17 Dec 2018 16:33:38 +0100	[thread overview]
Message-ID: <20181217153338.GS30879@dhcp22.suse.cz> (raw)
In-Reply-To: <CAKhyrx8E+43Ddqq7eBD3eomKp-GYeqehmo_G7ZO=d+oAi7GOqQ@mail.gmail.com>

On Mon 17-12-18 14:24:49, vijay nag wrote:
[...]
> Thanks for letting me know of this setting. However, there could be a
> third party daemons/processes that have THP in them. Do you think it is a
> good idea to make it cgroup aware ?

No, I do not really think this needs a cgroup support. Mostly because
the API scope for THP is way too complicated already and besides that
you can achieve what you want by setting PR_SET_THP_DISABLE and inherit
it down the road in your container.

-- 
Michal Hocko
SUSE Labs

      reply	other threads:[~2018-12-17 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17  8:26 vijay nag
2018-12-17  8:48 ` Mike Rapoport
2018-12-17  8:54   ` vijay nag
2018-12-17 15:33     ` Michal Hocko [this message]

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=20181217153338.GS30879@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rppt@linux.ibm.com \
    --cc=vijunag@gmail.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