From: vijay nag <vijunag@gmail.com>
To: rppt@linux.ibm.com
Cc: linux-mm@kvack.org
Subject: Re: Cgroups support for THP
Date: Mon, 17 Dec 2018 14:24:49 +0530 [thread overview]
Message-ID: <CAKhyrx8E+43Ddqq7eBD3eomKp-GYeqehmo_G7ZO=d+oAi7GOqQ@mail.gmail.com> (raw)
In-Reply-To: <20181217084836.GA22890@rapoport-lnx>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
On Mon, Dec 17, 2018 at 2:18 PM Mike Rapoport <rppt@linux.ibm.com> wrote:
> On Mon, Dec 17, 2018 at 01:56:40PM +0530, vijay nag wrote:
> > Hello Linux-MM,
> >
> > My containerized application which is suppose to have a very low RSS(by
> default
> > containers patterns are to have low memory footprint) seems to be
> getting its
> > BSS segment RSS bloated due to THPs. Although there is a huge zero page
> > support, the overhead seems to be at-least 2MB even when a byte is
> dirtied.
> > Also there are tune-able to disable this feature, but this seems to be a
> > system wide setting. Is there a plan to make this setting cgroup aware ?
>
> It's possible to control THP on per-mapping using madvise(MADV_NOHUGEPAGE)
> and per-process using prctl(PR_SET_THP_DISABLE).
>
> > Thanks,
> > Vijay Nag
>
> --
> Sincerely yours,
> Mike.
>
> 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 ?
[-- Attachment #2: Type: text/html, Size: 1391 bytes --]
next prev parent reply other threads:[~2018-12-17 8:55 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 [this message]
2018-12-17 15:33 ` Michal Hocko
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='CAKhyrx8E+43Ddqq7eBD3eomKp-GYeqehmo_G7ZO=d+oAi7GOqQ@mail.gmail.com' \
--to=vijunag@gmail.com \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.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