From: Sujit Karataparambil <sjt.kar@gmail.com>
To: SandeepKsinha <sandeepksinha@gmail.com>
Cc: Neil Brown <neilb@suse.de>, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
Date: Wed, 17 Jun 2009 14:44:59 +0530 [thread overview]
Message-ID: <921ca19c0906170214i2c70c2ebg7f59d525d9ba6307@mail.gmail.com> (raw)
In-Reply-To: <37d33d830906170148l74d95cd9g90738dfd278361c7@mail.gmail.com>
Sorry this was not my question. What I am asking is whether md is built on
top of the raid statically or is it an dynamic part of the raid array.
As with my experiance md is built statically. Your answer
> mddev->raid_disks can change, when you add disks and also in the mean
> while when you are updating the conf, the older conf might be being
> used at various other places.
does not speicify either. It seems to be from manual pages that tries
to administrate
raid array's.
next prev parent reply other threads:[~2009-06-17 9:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 15:24 [PATCH] md linear: Protecting mddev with rcu locks to avoid races in SandeepKsinha
2009-06-14 22:56 ` Neil Brown
2009-06-17 6:35 ` SandeepKsinha
2009-06-17 6:46 ` SandeepKsinha
2009-06-17 8:02 ` Sujit Karataparambil
2009-06-17 8:48 ` SandeepKsinha
2009-06-17 9:14 ` Sujit Karataparambil [this message]
2009-06-17 9:32 ` SandeepKsinha
2009-06-17 9:37 ` Sujit Karataparambil
2009-06-17 10:01 ` Neil Brown
[not found] ` <37d33d830906170315k4087d532nc2426879c2063fd7@mail.gmail.com>
2009-06-17 10:17 ` SandeepKsinha
2009-06-17 23:38 ` [PATCH] md linear: Protecting mddev with rcu locks to avoid races Neil Brown
2009-06-17 9:59 ` [PATCH] md linear: Protecting mddev with rcu locks to avoid races in Neil Brown
2009-06-17 6:50 ` 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=921ca19c0906170214i2c70c2ebg7f59d525d9ba6307@mail.gmail.com \
--to=sjt.kar@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=sandeepksinha@gmail.com \
/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