From: Matt Domsch <Matt_Domsch@dell.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: [RFCI] How best to partition MD/raid devices in 2.6
Date: Fri, 14 Nov 2003 15:44:23 -0600 [thread overview]
Message-ID: <20031114154423.A5587@lists.us.dell.com> (raw)
In-Reply-To: <20031114182927.GA8810@gtf.org>; from jgarzik@pobox.com on Fri, Nov 14, 2003 at 01:29:27PM -0500
> This brings up a tangent point... partitions on top of RAID are a new
> thing, which means that one has the chance to define the partition
> format.
>
> And I kinda like EFI partition format, a lot better than the other
> common ones...
Any reason why the current partition-mapping code couldn't be extended
to handle partition detection on a generic block device (which is what
MD presents I think) instead of a struct gendisk? Then it wouldn't
matter which scheme someone wanted to use - any scheme provided for in
the kernel (or userspace if partx were extended) could be used.
I'm partial to the EFI format too, but wouldn't want to write that
code a second time, once for normal disks, and once for md.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2003-11-14 21:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 3:11 [RFCI] How best to partition MD/raid devices in 2.6 Neil Brown
2003-11-14 5:09 ` viro
2003-11-14 5:32 ` Neil Brown
2003-11-14 5:21 ` Daniel Gryniewicz
2003-11-14 5:30 ` Neil Brown
2003-11-14 10:16 ` Lars Marowsky-Bree
2003-11-14 18:29 ` Jeff Garzik
2003-11-14 21:44 ` Matt Domsch [this message]
2003-11-14 22:45 ` viro
2003-11-17 0:46 ` Automatic Write Reallocation Enable, question? Guy
2003-11-17 0:46 ` Guy
2003-11-14 5:27 ` [RFCI] How best to partition MD/raid devices in 2.6 Daniel Pittman
2003-11-14 6:10 ` viro
2003-11-14 7:39 ` Luca Berra
2003-11-14 8:04 ` Paul Jakma
2003-11-14 8:04 ` Paul Jakma
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=20031114154423.A5587@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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 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.