From: Tejun Heo <tj@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Li Zefan <lizefan@huawei.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
mingo@kernel.org, peterz@infradead.org,
linaro-kernel@lists.linaro.org, patches@linaro.org,
linux-kernel@vger.kernel.org, Cgroups <cgroups@vger.kernel.org>
Subject: Re: [PATCH] cpusets: Allocate heap only when required
Date: Fri, 24 Jan 2014 05:59:52 -0500 [thread overview]
Message-ID: <20140124105952.GD4101@htj.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1401240243260.24372@chino.kir.corp.google.com>
Hey,
On Fri, Jan 24, 2014 at 02:51:12AM -0800, David Rientjes wrote:
> Nobody is depending on shit, the patch is removing a completely pointless
> memory allocation in braindead cpuset code. What you think is "harmful"
> or "more harmful" is irrelevant, but nobody said anything about depending
> on that behavior to do anything.
Weren't you talking something of that effect in memcg? Or was it
Michal? At any rate, I think you're missing the point why Li replied
that it's harmless. He, I think, meant that it doesn't make any
semantical difference to userland, so your reply saying that it's not
harmless listing the failure mode under memory pressure seemed
misleading, so I thought clarification was necessary. Probably my
(false?) memory of you talking about that contributed. Anyways, we
agree. Don't depend on it.
Thanks.
--
tejun
next prev parent reply other threads:[~2014-01-24 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 11:15 [PATCH] cpusets: Allocate heap only when required Viresh Kumar
2014-01-23 21:31 ` David Rientjes
2014-01-24 1:58 ` Li Zefan
2014-01-24 4:57 ` Viresh Kumar
2014-01-24 10:27 ` Tejun Heo
2014-01-24 10:33 ` Viresh Kumar
2014-01-24 10:40 ` Tejun Heo
2014-01-24 10:33 ` David Rientjes
2014-01-24 10:36 ` Tejun Heo
2014-01-24 10:51 ` David Rientjes
2014-01-24 10:59 ` Tejun Heo [this message]
2014-01-24 11:15 ` David Rientjes
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=20140124105952.GD4101@htj.dyndns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=patches@linaro.org \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=viresh.kumar@linaro.org \
/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