From: Nishanth Aravamudan <nacc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: [Kernel-janitors] Re: [PATCH] md: replace schedule_timeout() with
Date: Mon, 26 Jul 2004 17:31:06 +0000 [thread overview]
Message-ID: <20040726173106.GC1897@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0407240731440.16034@devserv.devel.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
On Sat, Jul 24, 2004 at 07:33:31AM -0400, Ingo Molnar wrote:
>
> On Fri, 23 Jul 2004, Nishanth Aravamudan wrote:
>
> > --- linux-vanilla/drivers/md/md.c 2004-06-16 05:19:03.000000000 +0000
> > +++ linux-dev/drivers/md/md.c 2004-07-12 18:47:53.000000000 +0000
> > @@ -3438,8 +3438,7 @@ static void md_do_sync(mddev_t *mddev)
> > if (currspeed > sysctl_speed_limit_min) {
> > if ((currspeed > sysctl_speed_limit_max) ||
> > !is_mddev_idle(mddev)) {
> > - current->state = TASK_INTERRUPTIBLE;
> > - schedule_timeout(HZ/4);
> > + msleep(250);
>
> well, it's not 100% equivalent because msleep() is uninterruptible so
> stoppage of the md thread (upon shutdown) will occur with only a 250 msec
> delay. Someone should add a msleep_interruptible() function to
> kernel/timer.c.
You are exactly right. That's what I tried to indicated in my posts.
There isn't any msleep_interruptible() unfortunately, so the code can just
be left as is.
Thanks,
Nish
[-- 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
prev parent reply other threads:[~2004-07-26 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 11:33 [Kernel-janitors] Re: [PATCH] md: replace schedule_timeout() with Ingo Molnar
2004-07-26 17:31 ` Nishanth Aravamudan [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=20040726173106.GC1897@us.ibm.com \
--to=nacc@us.ibm.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.