From: Neil Brown <neilb@suse.de>
To: Sujit Karataparambil <sjt.kar@gmail.com>
Cc: SandeepKsinha <sandeepksinha@gmail.com>,
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 20:01:17 +1000 [thread overview]
Message-ID: <19000.48877.539325.500493@notabene.brown> (raw)
In-Reply-To: message from Sujit Karataparambil on Wednesday June 17
On Wednesday June 17, sjt.kar@gmail.com wrote:
> Sorry what your patch claims is that the raid array can change the number of
> array's otherwise there is no need for an rcu.
>
> > What makes you think that md is static when you array itself can grow.
> > md contains information pertaining to the array it holds.
>
> This is what I saying my the md is built statically on top of the raid.
md/linear allows an array to grow while it is only. You can add a
drive to a 'linear' array and it will become larger to include that
drive. So the array is not completely static.
NeilBrown
next prev parent reply other threads:[~2009-06-17 10:01 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
2009-06-17 9:32 ` SandeepKsinha
2009-06-17 9:37 ` Sujit Karataparambil
2009-06-17 10:01 ` Neil Brown [this message]
[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=19000.48877.539325.500493@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=sandeepksinha@gmail.com \
--cc=sjt.kar@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