From: Paul Clements <paul.clements@steeleye.com>
To: Al Boldi <a1426z@gawab.com>
Cc: NeilBrown <neilb@cse.unsw.edu.au>, Andrew Morton <akpm@osdl.org>,
linux-raid@vger.kernel.org
Subject: Re: [PATCH md 006 of 6] Add write-behind support for md/raid1
Date: Fri, 12 Aug 2005 08:15:02 -0400 [thread overview]
Message-ID: <42FC92C6.7060604@steeleye.com> (raw)
In-Reply-To: <200508120922.52689.a1426z@gawab.com>
Al Boldi wrote:
> NeilBrown wrote:
>
>>If a device is flagged 'WriteMostly' and the array has a bitmap,
>>and the bitmap superblock indicates that write_behind is allowed,
>>then write_behind is enabled for WriteMostly devices.
>
>
> Nice, but why is it dependent on WriteMostly?
WriteMostly is just a flag that tells us which devices will get the
write-behinds, and which will not. You'll be able to mix any combination
of WriteMostly devices and normal devices in a raid1.
--
Paul
next prev parent reply other threads:[~2005-08-12 12:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 7:22 [PATCH md 000 of 6] Introduction NeilBrown
2005-08-11 7:22 ` [PATCH md 002 of 6] Don't allow new md/bitmap file to be set if one already exists NeilBrown
2005-08-11 7:22 ` [PATCH md 003 of 6] Improve handling of bitmap initialisation NeilBrown
2005-08-11 7:22 ` [PATCH md 001 of 6] Make sure mddev->bitmap_offset gets cleared between array instantiations NeilBrown
2005-08-11 7:22 ` [PATCH md 004 of 6] All hot-add and hot-remove of md intent logging bitmaps NeilBrown
2005-08-11 7:22 ` [PATCH md 006 of 6] Add write-behind support for md/raid1 NeilBrown
2005-08-12 6:22 ` Al Boldi
2005-08-12 12:15 ` Paul Clements [this message]
2005-08-13 5:00 ` Al Boldi
2005-08-14 22:24 ` Neil Brown
2005-08-15 4:45 ` Al Boldi
2005-08-14 22:16 ` Neil Brown
2005-08-11 7:22 ` [PATCH md 005 of 6] Support write-mostly device in raid1 NeilBrown
2005-08-11 8:51 ` RAID5 spare change djani22
2005-08-11 10:08 ` Neil Brown
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=42FC92C6.7060604@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=a1426z@gawab.com \
--cc=akpm@osdl.org \
--cc=linux-raid@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.