All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rakib Mullick <rakib.mullick@gmail.com>
To: Hillf Danton <dhillf@gmail.com>
Cc: Michael Wang <wangyun@linux.vnet.ibm.com>,
	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:26:24 +0600	[thread overview]
Message-ID: <CADZ9YHio6QkM3mQJrPFd-Pac_+o5BcHx=Qb7ppfx4OKgfq4Fhg@mail.gmail.com> (raw)
In-Reply-To: <CAJd=RBCp+Pdkip7O+xRhGFU2kpFyJQmxeXR5dJu7xmQ2uNrW9Q@mail.gmail.com>

On Mon, Jan 16, 2012 at 7:00 PM, Hillf Danton <dhillf@gmail.com> wrote:
> On Mon, Jan 16, 2012 at 4:27 PM, Rakib Mullick <rakib.mullick@gmail.com> wrote:
>> On Mon, Jan 16, 2012 at 1:53 PM, Michael Wang
>> <wangyun@linux.vnet.ibm.com> wrote:
>>> I think the task in rq->wake_list should already have state:TASK_WAKING,
>>> because it's a wake list.
>>>
>> But, what I got by means of TASK_WAKING is this task is about to RUN,
>> very soon it'll have TASK_RUNNING state. And, if I hadn't miss any
>> portion of code, then rq->wake_list doesn't have TASK_WAKING state.
>>
> Hi Rakib
>
> The question maybe settled down by adding a BUG_ON or similar to
> capture what you concern, and wait results while drinking tea or
> coffee.
>
Hi Hillf,

Thanks for your suggestions, will apply this technique when some new
confusion arises. Now, it's quite clear :)

Thanks,
Rakib

      reply	other threads:[~2012-01-16 17:26 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
2012-01-16 13:00             ` Hillf Danton
2012-01-16 17:26               ` Rakib Mullick [this message]

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='CADZ9YHio6QkM3mQJrPFd-Pac_+o5BcHx=Qb7ppfx4OKgfq4Fhg@mail.gmail.com' \
    --to=rakib.mullick@gmail.com \
    --cc=dhillf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.