public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Thornber <joe@fib011235813.fsnet.co.uk>
To: lvm-devel@sistina.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [lvm-devel] dm fs?
Date: Mon, 6 Jan 2003 09:43:17 +0000	[thread overview]
Message-ID: <20030106094316.GC2543@reti> (raw)
In-Reply-To: <20030105213728.GA8239@gtf.org>

On Sun, Jan 05, 2003 at 04:37:28PM -0500, Jeff Garzik wrote:
> What is the status of dmfs going into mainline?
> 
> I saw that Greg KH posted a patch with some corrections to dmfs for
> 2.5.50?
> 
> IMO it would be nice to have a kernel config option that makes the
> ioctl method optional when dmfs is set to y or m in kernel config.
> That will not only save a bit of code space, but it will also serve to
> encourage use of dmfs.  :)

The last version I released is here: 

http://people.sistina.com/~thornber/patches/2.5-unstable/2.5.51/2.5.51-dmfs-1.tar.bz2

There are still a couple of easy to fix issues with it (eg. the
kmalloc while a spin lock is held that Andrew Morton pointed out :).

Both Andrew Morton and Greg KH expressed concerns with the way I've
mapped the dm semantics onto the filesystem
(http://marc.theaimsgroup.com/?l=linux-kernel&m=103975736919315&w=2).
So Greg is currently trying to get a sysfs interface working.

We need to get a concensus of opinion in the community as to what is a
good interface.  I'm not going to be rushed into including something
in dm that could cause critism for years to come.  dmfs is what
Alasdair Kergon and I have proposed, we're just waiting for an
alternative to kick off the discussions ATM.

- Joe

  reply	other threads:[~2003-01-06  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-05 21:37 dm fs? Jeff Garzik
2003-01-06  9:43 ` Joe Thornber [this message]
2003-01-07  1:44   ` [lvm-devel] " Greg KH

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=20030106094316.GC2543@reti \
    --to=joe@fib011235813.fsnet.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvm-devel@sistina.com \
    /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