All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Christoph Hellwig <hch@lst.de>
Cc: jejb@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/2] tidy up scsi_error_handler
Date: Fri, 28 Oct 2005 17:28:43 -0600	[thread overview]
Message-ID: <20051028232843.GC21871@parisc-linux.org> (raw)
In-Reply-To: <20051028230155.GA13083@lst.de>

On Sat, Oct 29, 2005 at 01:01:55AM +0200, Christoph Hellwig wrote:
>  	/*
> -	 * Note - we always use TASK_INTERRUPTIBLE even if the module
> -	 * was loaded as part of the kernel.  The reason is that
> -	 * UNINTERRUPTIBLE would cause this thread to be counted in
> -	 * the load average as a running process, and an interruptible
> -	 * wait doesn't.
> +	 * We use TASK_INTERRUPTIBLE so that the thread is not
> +	 * counted against the load average as a running process.
> +	 * We never actually get interrupted because kthread_run
> +	 * disables singal delivery for the created thread.

tpyo "signal".


      reply	other threads:[~2005-10-28 23:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28 23:01 [PATCH 1/2] tidy up scsi_error_handler Christoph Hellwig
2005-10-28 23:28 ` Matthew Wilcox [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=20051028232843.GC21871@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=hch@lst.de \
    --cc=jejb@steeleye.com \
    --cc=linux-scsi@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 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.