public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizefan@huawei.com>
To: David Rientjes <rientjes@google.com>
Cc: 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>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] cpusets: Allocate heap only when required
Date: Fri, 24 Jan 2014 09:58:21 +0800	[thread overview]
Message-ID: <52E1C8BD.2010500@huawei.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1401231330530.7313@chino.kir.corp.google.com>

Cc: Tejun

On 2014/1/24 5:31, David Rientjes wrote:
> On Thu, 23 Jan 2014, Viresh Kumar wrote:
> 
>> update_flag() routine uses heap only when spread_flag_changed is true. Otherwise
>> heap isn't used, but is allocated and freed unnecessarily.
>>

but harmless

>> Fix this by allocating heap only when required.
>>
>> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> 
> Acked-by: David Rientjes <rientjes@google.com>

Acked-by: Li Zefan <lizefan@huawei.com>

I would like this patch be picked up by Tejun. I'll send out a patchset
for cpuset which may have confliction with this one.


  reply	other threads:[~2014-01-24  1: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 [this message]
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
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=52E1C8BD.2010500@huawei.com \
    --to=lizefan@huawei.com \
    --cc=cgroups@vger.kernel.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=patches@linaro.org \
    --cc=peterz@infradead.org \
    --cc=rientjes@google.com \
    --cc=tj@kernel.org \
    --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