From: Dan Williams <dan.j.williams@intel.com>
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org, ed.ciechanowski@intel.com,
jacek.danecki@intel.com
Subject: [PATCH 0/3] Support setting the array size from userspace
Date: Thu, 05 Mar 2009 17:24:43 -0700 [thread overview]
Message-ID: <20090306002341.9882.61625.stgit@dwillia2-linux.ch.intel.com> (raw)
This series, against the 'md/for-next' branch, adds a sysfs attribute
for pinning the array size. As discussed earlier this is being
initiated to support the extra size rounding expected for Intel(R)
Matrix metadata arrays. For example a 20GB 4-disk raid5 array created
in the orom will have the per-device size set to 13981448 sectors. MD
calculates the array size as 41944320 sectors while the metadata records
the size as 41943040 sectors.
Tested against a raid5 grow from 4 to 5 disks, and a grow that attempts
to set the size smaller than the userspace pinned size. The attribute
displays 'default' when the size is unpinned, to aid debug.
---
Dan Williams (3):
md: 'array_size' sysfs attribute
md: centralize ->array_sectors modifications
md: add 'size' as a personality method
drivers/md/faulty.c | 14 ++++++
drivers/md/linear.c | 15 ++++++-
drivers/md/md.c | 97 +++++++++++++++++++++++++++++++++++++++++++++
drivers/md/multipath.c | 11 +++++
drivers/md/raid0.c | 22 ++++++++--
drivers/md/raid1.c | 19 +++++++--
drivers/md/raid10.c | 27 ++++++++++++-
drivers/md/raid5.c | 49 +++++++++++++++++------
include/linux/raid/md.h | 2 +
include/linux/raid/md_k.h | 2 +
10 files changed, 229 insertions(+), 29 deletions(-)
next reply other threads:[~2009-03-06 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 0:24 Dan Williams [this message]
2009-03-06 0:24 ` [PATCH 1/3] md: add 'size' as a personality method Dan Williams
2009-03-06 16:15 ` Andre Noll
2009-03-06 17:55 ` Dan Williams
2009-03-06 0:24 ` [PATCH 2/3] md: centralize ->array_sectors modifications Dan Williams
2009-03-06 0:24 ` [PATCH 3/3] md: 'array_size' sysfs attribute Dan Williams
2009-03-06 16:15 ` Andre Noll
2009-03-06 18:20 ` Dan Williams
2009-03-07 6:28 ` Dan Williams
2009-03-09 10:12 ` Andre Noll
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=20090306002341.9882.61625.stgit@dwillia2-linux.ch.intel.com \
--to=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=jacek.danecki@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).