Messages in this thread | | | Date | Tue, 28 Jan 2003 10:49:23 -0700 | From | Steven Dake <> | Subject | Re: New model for managing dev_t's for partitionable block devices |
| |
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? > >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |