All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willem Riede <osst@riede.org>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: Nishanth Aravamudan <nacc@us.ibm.com>,
	kernel-janitors@lists.osdl.org, osst-users@lists.sourceforge.net,
	linux-scsi@vger.kernel.org
Subject: Re: [Kernel-janitors] [PATCH] Re: no set_current_state() before
Date: Tue, 13 Jul 2004 23:59:43 +0000	[thread overview]
Message-ID: <1089765906l.26949l.2l@serve.riede.org> (raw)
In-Reply-To: <29495f1d04071316362e782433@mail.gmail.com> (from nish.aravamudan@gmail.com on Tue, Jul 13, 2004 at 19:36:01 -0400)

On 07/13/2004 07:36:01 PM, Nish Aravamudan wrote:
> 
> The main reason I see for using msleep() instead is if the task should
> sleep for at least 100 ms. Using TASK_INTERRUPTIBLE (or really
> anything other than msleep()) is not guaranteed to sleep as long as
> requested. If that's ok / desired, then I won't convert it, of course.

There is no need for such guarantee. The current behavior is OK, by design.

Regards, Willem Riede.


_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

WARNING: multiple messages have this Message-ID (diff)
From: Willem Riede <osst@riede.org>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: Nishanth Aravamudan <nacc@us.ibm.com>,
	kernel-janitors@lists.osdl.org, osst-users@lists.sourceforge.net,
	linux-scsi@vger.kernel.org
Subject: Re: [Kernel-janitors] [PATCH] Re: no set_current_state() before schedule_timeout() (OSST)
Date: Wed, 14 Jul 2004 00:45:06 +0000	[thread overview]
Message-ID: <1089765906l.26949l.2l@serve.riede.org> (raw)
In-Reply-To: <29495f1d04071316362e782433@mail.gmail.com> (from nish.aravamudan@gmail.com on Tue, Jul 13, 2004 at 19:36:01 -0400)

On 07/13/2004 07:36:01 PM, Nish Aravamudan wrote:
> 
> The main reason I see for using msleep() instead is if the task should
> sleep for at least 100 ms. Using TASK_INTERRUPTIBLE (or really
> anything other than msleep()) is not guaranteed to sleep as long as
> requested. If that's ok / desired, then I won't convert it, of course.

There is no need for such guarantee. The current behavior is OK, by design.

Regards, Willem Riede.


  parent reply	other threads:[~2004-07-13 23:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 16:44 [Kernel-janitors] no set_current_state() before schedule_timeout() Nishanth Aravamudan
2004-07-13 17:10 ` Nishanth Aravamudan
2004-07-13 17:16 ` Nishanth Aravamudan
2004-07-13 17:20 ` Nishanth Aravamudan
2004-07-13 17:28 ` Nishanth Aravamudan
2004-07-13 17:31 ` Nishanth Aravamudan
2004-07-13 17:34 ` Nishanth Aravamudan
2004-07-13 17:34   ` no set_current_state() before schedule_timeout() (53C700) Nishanth Aravamudan
2004-07-13 17:36 ` [Kernel-janitors] no set_current_state() before schedule_timeout() Nishanth Aravamudan
2004-07-13 17:40 ` Nishanth Aravamudan
2004-07-13 17:40   ` no set_current_state() before schedule_timeout() (OSST) Nishanth Aravamudan
2004-07-13 22:27   ` [Kernel-janitors] [PATCH] Re: no set_current_state() before Willem Riede
2004-07-13 23:07     ` [PATCH] Re: no set_current_state() before schedule_timeout() (OSST) Willem Riede
2004-07-13 23:36     ` [Kernel-janitors] [PATCH] Re: no set_current_state() before Nish Aravamudan
2004-07-13 23:36       ` [Kernel-janitors] [PATCH] Re: no set_current_state() before schedule_timeout() (OSST) Nish Aravamudan
2004-07-13 23:56       ` [Kernel-janitors] [PATCH] Re: no set_current_state() before Nishanth Aravamudan
2004-07-13 23:56         ` [Kernel-janitors] [PATCH] Re: no set_current_state() before schedule_timeout() (OSST) Nishanth Aravamudan
2004-07-13 23:59       ` Willem Riede [this message]
2004-07-14  0:45         ` Willem Riede
2004-07-13 17:43 ` [Kernel-janitors] no set_current_state() before schedule_timeout() Nishanth Aravamudan
2004-07-13 17:43   ` no set_current_state() before schedule_timeout() (QLA1280) Nishanth Aravamudan
2004-07-13 17:45 ` [Kernel-janitors] no set_current_state() before schedule_timeout() Nishanth Aravamudan
2004-07-13 17:45   ` no set_current_state() before schedule_timeout() (scsi_lib) Nishanth Aravamudan
2004-07-13 17:51 ` [Kernel-janitors] no set_current_state() before schedule_timeout() Nishanth Aravamudan
2004-07-13 17:52 ` Nishanth Aravamudan
2004-07-13 17:54 ` Nishanth Aravamudan
2004-07-13 17:57 ` Nishanth Aravamudan

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=1089765906l.26949l.2l@serve.riede.org \
    --to=osst@riede.org \
    --cc=kernel-janitors@lists.osdl.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nacc@us.ibm.com \
    --cc=nish.aravamudan@gmail.com \
    --cc=osst-users@lists.sourceforge.net \
    /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.