public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Joseph Cordina <joseph.cordina@um.edu.mt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: wait queue process state
Date: Mon, 27 May 2002 08:49:50 -0700	[thread overview]
Message-ID: <20020527154950.GO14918@holomorphy.com> (raw)
In-Reply-To: <3CF2A0FB.8090507@um.edu.mt>

On Mon, May 27, 2002 at 05:11:23PM -0400, Joseph Cordina wrote:
> The reason I am asking is that I am working on scheduler activations 
> which allow new kernel threads to be created when a kernel thread blocks 
> inside the kernel. Yet this only works for INTERRUPTIBLE processes, I 
> was thinking of making it work also for NONINTERRUPTIBLE processes. Just 
> wondering if this would have any repurcusions. Also when a process 
> generates a page fault which causes a page to be retreived from the 
> filesystem, it such a process placed in the wait queue as 
> NONINTERRUPTIBLE also ?

filemap_nopage() from mm/filemap.c does wait_on_page() or some variant
thereof (2.5 has wait_on_page_locked()) in several places, and it's
placed into the TASK_UNINTERRUPTIBLE state while doing so.

Cheers,
Bill

  reply	other threads:[~2002-05-27 15:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27 21:11 wait queue process state Joseph Cordina
2002-05-27 15:49 ` William Lee Irwin III [this message]
2002-05-28  7:57 ` Terje Eggestad
2002-05-28 23:01   ` jw schultz
2002-05-28 23:05     ` Benjamin LaHaise
2002-05-29  0:21       ` Alan Cox
2002-05-29 10:58         ` David Woodhouse
2002-05-29 12:43           ` Alan Cox
2002-05-29 11:55             ` Roman Zippel
2002-05-29 13:29               ` Alan Cox
2002-05-29 11:56             ` David Woodhouse
2002-05-31 19:05               ` Theodore Ts'o
2002-05-29 11:25       ` Trond Myklebust

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=20020527154950.GO14918@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=joseph.cordina@um.edu.mt \
    --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