public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Joe Thornber <thornber@fib011235813.fsnet.co.uk>
Cc: lvm-devel@sistina.com, Jim McDonald <Jim@mcdee.net>,
	Andreas Dilger <adilger@turbolabs.com>,
	linux-lvm@sistina.com, linux-kernel@vger.kernel.org,
	evms-devel@lists.sourceforge.net
Subject: Re: [Evms-devel] Re: [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementation ready for beta testing
Date: Fri, 1 Feb 2002 04:55:18 -0500	[thread overview]
Message-ID: <20020201045518.A10893@devserv.devel.redhat.com> (raw)
In-Reply-To: <OFBCE93B66.F7B9C14E-ON85256B52.006B8AB3@raleigh.ibm.com> <20020131125211.A8934@fib011235813.fsnet.co.uk>
In-Reply-To: <20020131125211.A8934@fib011235813.fsnet.co.uk>; from thornber@fib011235813.fsnet.co.uk on Thu, Jan 31, 2002 at 12:52:11PM +0000

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

  reply	other threads:[~2002-02-01  9:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31 19:52 [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementation ready for beta testing Steve Pratt
2002-01-31 12:52 ` Joe Thornber
2002-02-01  9:55   ` Arjan van de Ven [this message]
2002-01-31 13:09     ` [Evms-devel] " Joe Thornber
2002-02-01 10:12       ` Arjan van de Ven
2002-01-31 13:35         ` Joe Thornber
2002-02-01 11:05         ` [Evms-devel] " Stephen C. Tweedie
2002-02-01 14:44         ` Alan Cox
2002-02-01 14:58           ` [Evms-devel] " Stephen C. Tweedie
2002-02-01 21:59   ` [evms-devel] [linux-lvm] " Kevin Corry
2002-01-31 21:51     ` Joe Thornber
2002-02-01 23:30     ` Alan Cox
2002-02-02 13:39     ` Andrew Clausen
2002-02-02 19:42       ` Alan Cox
2002-01-31 21:18 ` [Evms-devel] Re: [linux-lvm] Re: [lvm-devel] " Andrew Clausen

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=20020201045518.A10893@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=Jim@mcdee.net \
    --cc=adilger@turbolabs.com \
    --cc=evms-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-lvm@sistina.com \
    --cc=lvm-devel@sistina.com \
    --cc=thornber@fib011235813.fsnet.co.uk \
    /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