From: Andy Lutomirski <luto@myrealbox.com>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: puting task to TASK_INTERRUPTIBLE before adding it to an wait queue
Date: Fri, 17 Mar 2006 22:23:10 -0800 [thread overview]
Message-ID: <441BA74E.7090407@myrealbox.com> (raw)
In-Reply-To: <1142582503.7973.15.camel@homer>
Mike Galbraith wrote:
> On Fri, 2006-03-17 at 00:31 +0200, Yitzchak Eidus wrote:
>
>>the function worker_thread in kernel 2.6.15.6 first put the task to
>>TASK_INTERRUPTIBLE and only then add itself to an wait queue:
>> set_current_state(TASK_INTERRUPTIBLE);
>> while (!kthread_should_stop()) {
>> add_wait_queue(&cwq->more_work, &wait);
>
>
> See dusty old archives...
Also, preempted tasks get rescheduled regardless of state:
http://www.cs.helsinki.fi/linux/linux-kernel/2003-15/0402.html
--Andy
prev parent reply other threads:[~2006-03-18 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 22:31 puting task to TASK_INTERRUPTIBLE before adding it to an wait queue Yitzchak Eidus
2006-03-16 22:52 ` Yitzchak Eidus
2006-03-17 8:01 ` Mike Galbraith
2006-03-18 6:23 ` Andy Lutomirski [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=441BA74E.7090407@myrealbox.com \
--to=luto@myrealbox.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.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