All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] RE: [PATCH 3/22] block/cciss: replace schedule_timeout()
Date: Mon, 17 Jan 2005 22:30:47 +0000	[thread overview]
Message-ID: <20050117223047.GA29423@kroah.com> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF107DC01A4@cceexc23.americas.cpqcorp.net>

[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]

On Mon, Jan 17, 2005 at 04:14:10PM -0600, Miller, Mike (OS Dev) wrote:
> > From: Nishanth Aravamudan [mailto:nacc@us.ibm.com]
> > Hi,
> > 
> > Please consider applying.
> > 
> > I used msleep(10) here under the presumption that the 
> > schedule_timeout(1) was
> > written assuming that HZ=100 (as it used to be), which is
> > equivalent to 10 milliseconds. If the desire is actually for 
> > 1 ms or the minimal
> > sleep interval, then the patch can be changed appropriately. 
> > A similar assumption
> > as to the constant delay value was made in the other 
> > replacement, which can also
> > be appropriately adjusted.
> > 
> > Description: Change the delay logic in pollcomplete() to use 
> > msleep() and
> > time_before(). Instead of assuming schedule_timeout() will 
> > sleep exactly as
> > requested, use msleep(10) to guarantee minimally 10 
> > millisecond increments and
> > time_before() to guarantee stopping the loop as close to 20 
> > seconds as possible.
> > Also changes another occurrence of schedule_timeout() to msleep().
> > TASK_INTERRUPTIBLE is used in this case, but signals are not handled. 
> > 
> > Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
> 
> I still fail to see the benefits of this patch.

When HZ changed from 100 to 1000, your code went from sleeping 10ms to 1
ms.  Did you really mean that?  This way, your code always sleeps what
you expect it to sleep, no matter what the value of HZ.

thanks,

greg k-h


[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

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

  reply	other threads:[~2005-01-17 22:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-17 22:14 [KJ] RE: [PATCH 3/22] block/cciss: replace schedule_timeout() with Miller, Mike (OS Dev)
2005-01-17 22:30 ` Greg KH [this message]
2005-01-17 22:35 ` [KJ] " Nishanth Aravamudan
2005-01-18 19:00 ` [KJ] RE: [PATCH 3/22] block/cciss: replace schedule_timeout() Miller, Mike (OS Dev)

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=20050117223047.GA29423@kroah.com \
    --to=greg@kroah.com \
    --cc=kernel-janitors@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.