From: Nishanth Aravamudan <nacc@us.ibm.com>
To: mingo@redhat.com, neilb@cse.unsw.edu.au
Cc: akpm@osdl.org, linux-raid@vger.kernel.org
Subject: [-mm PATCH 24/32] drivers/md: fix-up schedule_timeout() usage
Date: Mon, 15 Aug 2005 11:24:36 -0700 [thread overview]
Message-ID: <20050815182436.GA2854@us.ibm.com> (raw)
In-Reply-To: <20050815180514.GC2854@us.ibm.com>
Description: Use schedule_timeout_interruptible() instead of
set_current_state()/schedule_timeout() to reduce kernel size.
Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
---
drivers/md/raid5.c | 3 +--
drivers/md/raid6main.c | 3 +--
2 files changed, 2 insertions(+), 4 deletions(-)
diff -urpN 2.6.13-rc5-mm1/drivers/md/raid5.c 2.6.13-rc5-mm1-dev/drivers/md/raid5.c
--- 2.6.13-rc5-mm1/drivers/md/raid5.c 2005-08-07 10:05:20.000000000 -0700
+++ 2.6.13-rc5-mm1-dev/drivers/md/raid5.c 2005-08-08 15:06:49.000000000 -0700
@@ -1522,8 +1522,7 @@ static sector_t sync_request(mddev_t *md
/* make sure we don't swamp the stripe cache if someone else
* is trying to get access
*/
- set_current_state(TASK_UNINTERRUPTIBLE);
- schedule_timeout(1);
+ schedule_timeout_uninterruptible(1);
}
spin_lock(&sh->lock);
set_bit(STRIPE_SYNCING, &sh->state);
diff -urpN 2.6.13-rc5-mm1/drivers/md/raid6main.c 2.6.13-rc5-mm1-dev/drivers/md/raid6main.c
--- 2.6.13-rc5-mm1/drivers/md/raid6main.c 2005-08-07 10:05:20.000000000 -0700
+++ 2.6.13-rc5-mm1-dev/drivers/md/raid6main.c 2005-08-08 15:06:55.000000000 -0700
@@ -1681,8 +1681,7 @@ static sector_t sync_request(mddev_t *md
/* make sure we don't swamp the stripe cache if someone else
* is trying to get access
*/
- set_current_state(TASK_UNINTERRUPTIBLE);
- schedule_timeout(1);
+ schedule_timeout_uninterruptible(1);
}
spin_lock(&sh->lock);
set_bit(STRIPE_SYNCING, &sh->state);
parent reply other threads:[~2005-08-15 18:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20050815180514.GC2854@us.ibm.com>]
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=20050815182436.GA2854@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@cse.unsw.edu.au \
/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;
as well as URLs for NNTP newsgroup(s).