From: Rakib Mullick <rakib.mullick@gmail.com>
To: Michael Wang <wangyun@linux.vnet.ibm.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Question] sched: Should nr_uninterruptible be decremented in ttwu_do_activate()?
Date: Mon, 16 Jan 2012 23:22:09 +0600 [thread overview]
Message-ID: <CADZ9YHgZcuoZ4_az3taqv2GJ_5mLKLmyOAUz2ZnA3G1YMLi1_w@mail.gmail.com> (raw)
In-Reply-To: <4F13EC3F.7050308@linux.vnet.ibm.com>
On Mon, Jan 16, 2012 at 3:22 PM, Michael Wang
<wangyun@linux.vnet.ibm.com> wrote:
> On 01/16/2012 04:27 PM, Rakib Mullick wrote:
>
>> On Mon, Jan 16, 2012 at 1:53 PM, Michael Wang
>
> I saw this is the way to enqueue wake_list:
>
> try_to_wake_up --> p->state = TASK_WAKING; --> ttwu_queue -->
> ttwu_queue_remote --> llist_add(&p->wake_entry, &cpu_rq(cpu)->wake_list)
>
Yes, right and if the task needs to wakeup on a remote CPU, then it
follows an reschedule IPI. But, what I was missing that, I wasn't sure
whether task gets added to wake_list only from ttwu_queue_remote() or
not. Now, I've found that - it is and you are right rq->wake_list only
have TASK_WAKING state.
> BTW, I'm just start to learn scheduler, may be I'm wrong, let's find out
> the right answer :)
>
I think it's quite clear to me now. And you are learning scheduler
well at-least better than me :)
Thanks,
Rakib
next prev parent reply other threads:[~2012-01-16 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 17:22 [Question] sched: Should nr_uninterruptible be decremented in ttwu_do_activate()? Rakib Mullick
2012-01-11 17:29 ` Peter Zijlstra
2012-01-12 6:09 ` Rakib Mullick
2012-01-12 7:25 ` Peter Zijlstra
2012-01-12 17:08 ` Rakib Mullick
2012-01-12 20:25 ` Peter Zijlstra
2012-01-16 7:53 ` Michael Wang
2012-01-16 8:27 ` Rakib Mullick
2012-01-16 9:22 ` Michael Wang
2012-01-16 17:22 ` Rakib Mullick [this message]
2012-01-16 13:00 ` Hillf Danton
2012-01-16 17:26 ` Rakib Mullick
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=CADZ9YHgZcuoZ4_az3taqv2GJ_5mLKLmyOAUz2ZnA3G1YMLi1_w@mail.gmail.com \
--to=rakib.mullick@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=wangyun@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.