From: Steven Dake <sdake@mvista.com>
To: Valdis.Kletnieks@vt.edu
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: New model for managing dev_t's for partitionable block devices
Date: Tue, 28 Jan 2003 10:49:23 -0700 [thread overview]
Message-ID: <3E36C2A3.4080102@mvista.com> (raw)
In-Reply-To: <200301281746.h0SHkOgM007373@turing-police.cc.vt.edu>
For newer revs of linux, I was specifically thinking of implementing
using device mapper to provide partition mapping so your thinking just
like me :) The only downside is device mapper becomes a required
component instead of being module capable since partition information is
needed before early boot is available to load modules.
Regards,
-steve
Valdis.Kletnieks@vt.edu wrote:
>On Tue, 28 Jan 2003 10:20:31 MST, Steven Dake <sdake@mvista.com> said:
>
>
>
>>Each physical disk would be assigned a minor number in a group of
>>majors. So assume a major was chosen of 150, 151, 152, 153, there would
>>be a total of 1024 physical disks that could be mapped. Then the device
>>mapper code could be used to provide partition devices in another
>>major/group of majors.
>>
>>
>
>This sounds suspiciously like the already-existing device mapper stuff
>used by LVM2. Maybe all that's needed is to add a hook to add a device
>mapper entry for each partition?
>
>
next prev parent reply other threads:[~2003-01-28 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 11:19 Probably buggy MP Table and ACPI doesn't works AnonimoVeneziano
[not found] ` <200301251135.52356.bp@dynastytech.com>
2003-01-25 18:04 ` AnonimoVeneziano
2003-01-28 17:20 ` New model for managing dev_t's for partitionable block devices Steven Dake
2003-01-28 17:46 ` Valdis.Kletnieks
2003-01-28 17:49 ` Steven Dake [this message]
2003-01-29 14:25 ` Horst von Brand
2003-01-30 16:57 ` Steven Dake
-- strict thread matches above, loose matches on Subject: below --
2003-01-30 11:53 Andrey Borzenkov
2003-01-30 12:34 ` Alex Tomas
2003-01-21 21:56 Fwd: 32bit dev_t Douglas Gilbert
2003-01-23 18:31 ` Kurt Garloff
2003-01-23 22:18 ` Christoph Hellwig
2003-01-24 18:29 ` Joel Becker
2003-01-27 22:51 ` Christoph Hellwig
2003-01-28 11:21 ` Alan Cox
2003-01-28 17:09 ` New model for managing dev_t's for partitionable block devices Steven Dake
2003-01-29 1:41 ` Bryan Henderson
2003-01-29 16:45 ` Steven Dake
2003-01-29 17:38 ` Andries Brouwer
2003-01-29 18:00 ` 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=3E36C2A3.4080102@mvista.com \
--to=sdake@mvista.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@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.