From: Yong Zhang <yong.zhang0@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Oleg Nesterov <oleg@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Li Zefan <lizf@cn.fujitsu.com>,
Miao Xie <miaox@cn.fujitsu.com>
Subject: Re: [PATCH 1/2] cpuset: fix cpuset_cpus_allowed_fallback() don't update tsk->rt.nr_cpus_allowed
Date: Thu, 19 May 2011 16:54:40 +0800 [thread overview]
Message-ID: <BANLkTi=GYr6XWyt50YaJ=WrDMFZ3aGAQkg@mail.gmail.com> (raw)
In-Reply-To: <1305794708.2466.7194.camel@twins>
On Thu, May 19, 2011 at 4:45 PM, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Mon, 2011-05-16 at 21:37 +0800, Yong Zhang wrote:
>>
>> But I'm afraid this patch still doesn't help.
>> If I understand your patch correctly, you just put the wake up to CPU_STARTING,
>> but it's still before CPU_ONLINE.\
>
> Well, that's the whole point really, CPU_ONLINE is terribly late. But
> did you perhaps mean to say its before we mark the cpu online?
I always try to express myself correctly(poor english :)
Precisely, it's before we mark the cpu active. sched_cpu_active()
is call when CPU_ONLINE.
Thanks,
Yong
>
>> Please check my mail to Paul's in this thread group.
>
> Not sure that made things any clearer.
>
--
Only stand for myself
next prev parent reply other threads:[~2011-05-19 8:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 14:20 [RFC PATCH] cpuset: fix cpuset_cpus_allowed_fallback() don't update tsk->rt.nr_cpus_allowed KOSAKI Motohiro
2011-04-28 16:11 ` Oleg Nesterov
2011-05-02 10:42 ` KOSAKI Motohiro
2011-05-02 10:55 ` [PATCH 1/2] " KOSAKI Motohiro
2011-05-11 16:05 ` Peter Zijlstra
2011-05-13 5:48 ` KOSAKI Motohiro
2011-05-13 6:42 ` Yong Zhang
2011-05-13 7:33 ` KOSAKI Motohiro
2011-05-13 7:43 ` Yong Zhang
2011-05-13 9:34 ` KOSAKI Motohiro
2011-05-13 17:02 ` Peter Zijlstra
2011-05-14 11:17 ` KOSAKI Motohiro
2011-05-16 13:37 ` Yong Zhang
2011-05-19 8:45 ` Peter Zijlstra
2011-05-19 8:54 ` Yong Zhang [this message]
2011-05-15 18:55 ` Paul E. McKenney
2011-05-16 13:26 ` Yong Zhang
2011-05-19 6:06 ` [PATCH v2 1/2] rcu: don't bind offline cpu KOSAKI Motohiro
2011-05-19 6:08 ` [PATCH v2 2/2] cpuset: fix cpuset_cpus_allowed_fallback() don't update tsk->rt.nr_cpus_allowed KOSAKI Motohiro
2011-05-28 16:35 ` [tip:sched/urgent] cpuset: Fix cpuset_cpus_allowed_fallback(), " tip-bot for KOSAKI Motohiro
2011-06-20 10:20 ` Peter Zijlstra
2011-06-21 9:54 ` KOSAKI Motohiro
2011-05-19 8:34 ` [PATCH v2 1/2] rcu: don't bind offline cpu Peter Zijlstra
2011-05-19 8:50 ` KOSAKI Motohiro
2011-05-19 9:41 ` Peter Zijlstra
2011-05-19 10:12 ` KOSAKI Motohiro
2011-05-19 11:41 ` Peter Zijlstra
2011-05-20 22:46 ` Paul E. McKenney
2011-05-19 8:55 ` Peter Zijlstra
2011-05-02 10:56 ` [PATCH 2/2] sched, cpuset: introduce do_set_cpus_allowed() helper function KOSAKI Motohiro
2011-05-02 12:58 ` [RFC PATCH] cpuset: fix cpuset_cpus_allowed_fallback() don't update tsk->rt.nr_cpus_allowed Paul E. McKenney
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='BANLkTi=GYr6XWyt50YaJ=WrDMFZ3aGAQkg@mail.gmail.com' \
--to=yong.zhang0@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=miaox@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=oleg@redhat.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;
as well as URLs for NNTP newsgroup(s).