LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andre Noll <maan@systemlinux.org>
To: NeilBrown <neilb@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
"K.Tanaka" <k-tanaka@ce.jp.nec.com>
Subject: Re: [PATCH 001 of 9] md: Fix deadlock in md/raid1 and md/raid10 when handling a read error.
Date: Mon, 3 Mar 2008 16:54:49 +0100 [thread overview]
Message-ID: <20080303155449.GA32242@skl-net.de> (raw)
In-Reply-To: <1080303001705.23577@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]
On 11:17, NeilBrown wrote:
> So we create a new function 'flush_pending_writes' to give that attention,
> and call it in freeze_array to be sure that we aren't waiting on raid1d.
Two minor remarks:
> +static int flush_pending_writes(conf_t *conf)
> +{
> + /* Any writes that have been queued but are awaiting
> + * bitmap updates get flushed here.
> + * We return 1 if any requests were actually submitted.
> + */
> + int rv = 0;
> +
> + spin_lock_irq(&conf->device_lock);
>
> + if (conf->pending_bio_list.head) {
> + struct bio *bio;
> + bio = bio_list_get(&conf->pending_bio_list);
> + blk_remove_plug(conf->mddev->queue);
> + spin_unlock_irq(&conf->device_lock);
> + /* flush any pending bitmap writes to disk
> + * before proceeding w/ I/O */
> + bitmap_unplug(conf->mddev->bitmap);
> +
> + while (bio) { /* submit pending writes */
> + struct bio *next = bio->bi_next;
> + bio->bi_next = NULL;
> + generic_make_request(bio);
> + bio = next;
> + }
> + rv = 1;
> + } else
> + spin_unlock_irq(&conf->device_lock);
> + return rv;
> +}
Do we really need to take the spin lock in the common case where
conf->pending_bio_list.head is NULL? If not, the above could be
optimized to the slightly faster and better readable
struct bio *bio;
if (!conf->pending_bio_list.head)
return 0;
spin_lock_irq(&conf->device_lock);
bio = bio_list_get(&conf->pending_bio_list);
...
spin_unlock_irq(&conf->device_lock);
return 1;
> diff .prev/drivers/md/raid1.c ./drivers/md/raid1.c
> --- .prev/drivers/md/raid1.c 2008-02-22 15:45:35.000000000 +1100
> +++ ./drivers/md/raid1.c 2008-02-22 15:45:35.000000000 +1100
> @@ -592,6 +592,37 @@ static int raid1_congested(void *data, i
> }
>
>
> +static int flush_pending_writes(conf_t *conf)
> +{
[snip]
Any chance to avoid this code duplication?
Regards
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-03 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 0:16 [PATCH 000 of 9] md: Introduction EXPLAIN PATCH SET HERE NeilBrown
2008-03-03 0:17 ` [PATCH 001 of 9] md: Fix deadlock in md/raid1 and md/raid10 when handling a read error NeilBrown
2008-03-03 15:54 ` Andre Noll [this message]
2008-03-04 6:08 ` Neil Brown
2008-03-04 11:29 ` Andre Noll
2008-03-06 3:29 ` Neil Brown
2008-03-06 10:51 ` Andre Noll
2008-03-03 0:17 ` [PATCH 002 of 9] md: Reduce CPU wastage on idle md array with a write-intent bitmap NeilBrown
2008-03-03 0:17 ` [PATCH 003 of 9] md: Guard against possible bad array geometry in v1 metadata NeilBrown
2008-03-03 0:17 ` [PATCH 004 of 9] md: Clean up irregularity with raid autodetect NeilBrown
2008-03-03 0:17 ` [PATCH 005 of 9] md: Make sure a reshape is started when device switches to read-write NeilBrown
2008-03-03 0:17 ` [PATCH 006 of 9] md: Lock access to rdev attributes properly NeilBrown
2008-03-03 0:17 ` [PATCH 007 of 9] md: Don't attempt read-balancing for raid10 'far' layouts NeilBrown
2008-03-03 0:17 ` [PATCH 008 of 9] md: Fix possible raid1/raid10 deadlock on read error during resync NeilBrown
2008-03-03 0:18 ` [PATCH 009 of 9] md: The md RAID10 resync thread could cause a md RAID10 array deadlock NeilBrown
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=20080303155449.GA32242@skl-net.de \
--to=maan@systemlinux.org \
--cc=akpm@linux-foundation.org \
--cc=k-tanaka@ce.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--subject='Re: [PATCH 001 of 9] md: Fix deadlock in md/raid1 and md/raid10 when handling a read error.' \
/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
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).