On Thu, Jan 31, 2002 at 01:52:29PM -0600, Steve Pratt wrote:
> Joe Thornber wrote:
> >On Wed, Jan 30, 2002 at 10:03:40PM +0000, Jim McDonald wrote:
> >> Also, does/where does this fit in with EVMS?
>
> >EVMS differs from us in that they seem to be trying to move the whole
> >application into the kernel,
>
> No, not really. We only put in the kernel the things that make sense to be
> in the kernel, discovery logic, ioctl support, I/O path. All configuration
> is handled in user space.
The notion of "volume group" and "physical volume", etc. does
not exist in the device mapper.
It is really much lower-level.
As it is, it could be used for partitioning as well, with a single
LOC changed. In fact, I imagine it's a 100 LOC or so in libparted to
get partprobe to use it. Then we could retire all partition code
from the kernel :)
> > whereas we've taken the opposite route
> >and stripped down the kernel side to just provide services.
>
> Then why does snapshot.c in device mapper have a read_metadata function
> which populates the exception table from on disk metadata? Seems like you
> agree with us that having metadata knowledge in the kernel is a GOOD thing.
It's good to *support* reading metadata, but better to not require it.
> Since device_mapper does not support in kernel discovery, and EVMS relies
> on this, it would be very difficult to change EVMS to use device_mapper.
Why? Just because device_mapper itself doesn't support discovery
doesn't mean you can't do the discovery for it, and setup the
devices in-kernel.
I think a bigger issue will be the difference in interface for
EVMS stuff, like all the plugin ioctls... it would be great if
you could:
* decouple the evms runtime (kernel code) from the evms
engine (userland). Something like libparted's PedArchitecture
would be nice.
* get everyone in the linux community to agree on some standard
ioctl's that provide an interface for everything that evms
(and everyone else) needs.
How hard is this to do?
Andrew
-
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/
This archive was generated by hypermail 2b29 : Thu Jan 31 2002 - 21:01:39 EST