lkml.org 
[lkml]   [2002]   [Feb]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [Evms-devel] Re: [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementation ready for beta testing
    On Thu, Jan 31, 2002 at 12:52:11PM +0000, Joe Thornber wrote:
    > 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.
    >
    > There's still a *lot* of code in there; > 26,000 lines in fact.
    > Whereas device-mapper weighs in at ~2,600 lines. This is just because
    > you've decided to take a different route from us, you may be proven to
    > be correct.

    There is one thing that might spoil the device-mapper "just simple stuff
    only" thing: moving active volumes around. Doing that in userspace reliably
    is impossible and basically needs to be done in kernelspace (it's an
    operation comparable with raid1 resync, a not even that hard in kernel
    space). However, that sort of automatically requires kernelspace to know
    about volumes, and from there it's a small step....

    Greetings,
    Arjan van de Ven
    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 13:23    [W:0.020 / U:0.960 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site