Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org
Subject: [PATCH md 0 of 7] Introduction
Date: Wed, 08 Sep 2004 12:48:09 +1000	[thread overview]
Message-ID: <20040908124236.20651.patches@notabene> (raw)

Following are 7 patches for md in 2.6.8-rc1-mm2

They all grew out of a desire to redo the locking in unplug_slave.
Getting and dropping a spinlock so often for very little gain (it
would be nearly impossible to lose the relevant race) really bothered
me.

I finally figured that I could reply it with rcu locking which is very
light wait, and quite up to the task.

One the way I found an number of inconsistencies that needed cleaning
up and even a few bugs to fix.
The first 6 patches deal with these inconsistencies and bugs.  The
last redoes the locking for adding/removing/accessing devices within
md personalities.



             reply	other threads:[~2004-09-08  2:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08  2:48 NeilBrown [this message]
2004-09-08  2:48 ` [PATCH md 1 of 7] Remove md_flush_all NeilBrown
2004-09-08  2:48 ` [PATCH md 2 of 7] Make retry_list non-global in raid1 and multipath NeilBrown
2004-09-08  2:48 ` [PATCH md 4 of 7] Rationalise unplug functions in md NeilBrown
2004-09-08  2:48 ` [PATCH md 3 of 7] Rationalise issue_flush function in md personalities NeilBrown
2004-09-08  2:48 ` [PATCH md 7 of 7] Modify locking when accessing subdevices in md NeilBrown
2004-09-08  2:48 ` [PATCH md 5 of 7] Make sure md always uses rdev_dec_pending properly NeilBrown
2004-09-08  2:48 ` [PATCH md 6 of 7] Fix two little bugs in raid10 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=20040908124236.20651.patches@notabene \
    --to=neilb@cse.unsw.edu.au \
    --cc=akpm@osdl.org \
    --cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox