From: David Rientjes <rientjes@google.com>
To: Mike Galbraith <bitbucket@online.de>
Cc: Robin Holt <holt@sgi.com>, Alex Thorlton <athorlton@sgi.com>,
linux-kernel@vger.kernel.org, Li Zefan <lizefan@huawei.com>,
Rob Landley <rob@landley.net>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
linux-doc@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2] Make transparent hugepages cpuset aware
Date: Thu, 20 Jun 2013 13:37:36 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1306201334460.24145@chino.kir.corp.google.com> (raw)
In-Reply-To: <1371697844.5739.29.camel@marge.simpson.net>
On Thu, 20 Jun 2013, Mike Galbraith wrote:
> > I'm suspecting that you're referring to enlarged rss because of
> > khugepaged's max_ptes_none and because you're abusing the purpose of
> > cpusets for containerization.
>
> Why is containerization an abuse? What's wrong with renting out chunks
> of a big box farm on the fly like a task motel? If a realtime customer
> checks in, he's not gonna be thrilled about sharing a room.
>
We "abused" cpusets for containerization for years, I'm not implying any
negative connotation to it, see the
Documentation/x86/x86_64/fake-numa-for-cpusets document that I wrote. It
doesn't suggest that we should be controlling thp through cpusets; if he's
complaining about static binaries where he can't use a malloc hook then
why not make it per-process so users don't have to configure cpusets to
control it?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-06-20 20:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 16:14 Alex Thorlton
2013-06-11 22:20 ` David Rientjes
2013-06-18 16:45 ` Alex Thorlton
2013-06-19 0:01 ` David Rientjes
2013-06-19 9:32 ` Robin Holt
2013-06-19 21:24 ` David Rientjes
2013-06-20 2:27 ` Robin Holt
2013-06-20 2:43 ` David Rientjes
2013-06-20 3:10 ` Mike Galbraith
2013-06-20 20:37 ` David Rientjes [this message]
2013-07-29 19:42 ` Alex Thorlton
2013-06-20 3:34 ` Li Zefan
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.02.1306201334460.24145@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=athorlton@sgi.com \
--cc=bitbucket@online.de \
--cc=hannes@cmpxchg.org \
--cc=holt@sgi.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=mgorman@suse.de \
--cc=riel@redhat.com \
--cc=rob@landley.net \
--cc=xiaoguangrong@linux.vnet.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