From: Kurt Garloff <garloff@suse.de>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>,
linux-scsi@vger.kernel.org, Badari Pulavarty <pbadari@us.ibm.com>,
Matthew Wilcox <willy@debian.org>,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: lots and lots of disks again
Date: Tue, 10 Feb 2004 21:58:33 +0100 [thread overview]
Message-ID: <20040210205833.GT4010@tpkurt.garloff.de> (raw)
In-Reply-To: <20040210211002.A1534@pclin040.win.tue.nl>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Hi Andries,
On Tue, Feb 10, 2004 at 09:10:02PM +0100, Andries Brouwer wrote:
> + * major p2 disc2 disc p1
> + * |............|..|..........|....|....| <- dev_t
> + * 31 20 17 8 7 4 3 0
[...]
>
> It is true that the first step needed is some agreement on
> how to assign device numbers to disks and their partitions.
>
> The above suggestion is really ugly, however.
Nice! Ask two people and you'll get three opinions.
> I can hardly imagine that we would like to start such crap
> while still in the design phase.
We maintain backwards compatibility.
We need some bit shuffling and the rest is straightforward.
As we are pretty sure to not need beyong 256k disks, we reserve two
extra bits for the partition (though we can't currently use it).
The only alternative that I see is leaving the old majors alone
and starting a new scheme with new majors. Not really nice either;
if you think about supporting > 16 partitions, it's even very
inconsistent.
I don't see what's crappy with the suggestion. Tell us!
Regards,
--
Kurt Garloff <garloff@suse.de> Cologne, DE
SUSE LINUX AG, Nuernberg, DE SUSE Labs (Head)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-10 20:59 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 10:45 lots and lots of disks again Andrew Morton
2004-02-10 11:04 ` Kurt Garloff
2004-02-10 11:26 ` Kurt Garloff
2004-02-10 13:39 ` Christoph Hellwig
2004-02-10 15:47 ` Kurt Garloff
2004-02-10 15:52 ` Christoph Hellwig
2004-02-10 16:08 ` Kurt Garloff
2004-02-10 20:10 ` Andries Brouwer
2004-02-10 20:11 ` Matthew Wilcox
2004-02-10 20:58 ` Kurt Garloff [this message]
2004-02-10 21:21 ` viro
2004-02-10 21:34 ` Kurt Garloff
2004-02-10 21:42 ` viro
2004-02-10 22:28 ` Kurt Garloff
2004-02-10 18:26 ` Andrew Morton
2004-02-11 14:56 ` Kurt Garloff
2004-02-11 21:28 ` Andrew Morton
2004-02-11 22:09 ` Kurt Garloff
2004-02-11 22:29 ` Andrew Morton
2004-02-11 22:53 ` viro
2004-02-12 15:00 ` Kurt Garloff
2004-02-12 15:20 ` James Bottomley
2004-02-12 15:57 ` viro
2004-02-12 16:18 ` Kurt Garloff
2004-02-12 16:43 ` James Bottomley
2004-02-16 12:40 ` Kurt Garloff
2004-02-16 22:57 ` Andries Brouwer
2004-02-17 0:56 ` James Bottomley
2004-02-17 7:57 ` Kurt Garloff
2004-02-17 15:08 ` James Bottomley
2004-02-17 15:28 ` Matthew Wilcox
2004-02-17 14:49 ` Andries Brouwer
2004-02-17 15:18 ` James Bottomley
2004-02-17 15:27 ` Kurt Garloff
2004-02-29 16:41 ` James Bottomley
2004-02-29 23:31 ` Kurt Garloff
2004-03-03 19:30 ` Mike Anderson
2004-03-03 19:55 ` Kurt Garloff
2004-02-17 15:50 ` Andries Brouwer
2004-02-17 17:57 ` James Bottomley
2004-02-17 18:44 ` Andries Brouwer
2004-02-13 0:05 ` Kurt Garloff
2004-02-16 12:31 ` Kurt Garloff
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=20040210205833.GT4010@tpkurt.garloff.de \
--to=garloff@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=aebr@win.tue.nl \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=willy@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox