mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: keventd_create_kthread
Date: Thu, 19 Feb 2004 15:35:50 +0530	[thread overview]
Message-ID: <20040219100549.GA27018@in.ibm.com> (raw)
In-Reply-To: <20040219001011.6245f163.akpm@osdl.org>

On Thu, Feb 19, 2004 at 08:12:19AM +0000, Andrew Morton wrote:
> However, if that wake_up_process() comes too early we'll just flip the new
> thread out of TASK_INTERUPTIBLE into TASK_RUNNING and the schedule() in
> kthread() will fall straight through.  So perhaps we can simply remove the
> wait_task_inactive()?

If wake_up_process() comes too early (when the target task is still
in TASK_RUNNING state), then won't wake_up_process() be a no-op?
In which case, the target kthread will miss a wake-up event 
(kthread_start/kthread_stop)?

-- 


Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017

  parent reply	other threads:[~2004-02-19 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040218004648.7471bb37.akpm@osdl.org>
2004-02-18 23:12 ` keventd_create_kthread Rusty Russell
2004-02-19  7:46   ` keventd_create_kthread Ingo Molnar
2004-02-19  8:10     ` keventd_create_kthread Andrew Morton
2004-02-19  8:16       ` keventd_create_kthread Ingo Molnar
2004-02-19 10:05       ` Srivatsa Vaddagiri [this message]
2004-02-19 10:10         ` keventd_create_kthread Andrew Morton
2004-02-19  9:46     ` keventd_create_kthread Rusty Russell

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=20040219100549.GA27018@in.ibm.com \
    --to=vatsa@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rusty@rustcorp.com.au \
    /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
all inboxes | Powered by JetHome®