public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: roland <devzero@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is there a COW inside the kernel ?
Date: Fri, 3 Mar 2006 10:25:27 -0500	[thread overview]
Message-ID: <20060303152527.GA3536@ccure.user-mode-linux.org> (raw)
In-Reply-To: <043101c63e9c$86e9d710$0200000a@aldipc>

On Fri, Mar 03, 2006 at 09:29:02AM +0100, roland wrote:
> hello !
> 
> is there an equivalent of something like
> 
> cowloop ( http://www.atconsultancy.nl/cowloop/total.html ) or md based cow 
> device ( http://www.cl.cam.ac.uk/users/br260/doc/report.pdf ),
> 
> i.e. a feature called "Copy On Write Blockdevice" inside the current or the 
> near-future mainline kernel (besides UserModeLinux Arch)?
> can someone help out with some information ?

Miklos Szeredi announced mountlo a few days ago - this uses a UML to
export a filesystem to the host through FUSE.  It's intended to allow
non-privileged loopback mounting of normal file system images, but
presumably will export a COW block device as well.

I'm doing something similar, and using FUSE to export the entire UML
filesystem to the host.

These aren't specifically COW drivers, but they have the same effect
as long as you have a UML with your COW device mounted.

				Jeff

      parent reply	other threads:[~2006-03-03 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-03  8:29 is there a COW inside the kernel ? roland
2006-03-03 13:33 ` Jan Engelhardt
2006-03-03 14:19 ` Alasdair G Kergon
2006-03-03 14:28 ` Kevin Corry
2006-03-03 21:29   ` roland
2006-03-03 22:39     ` Kevin Corry
2006-03-04  5:35     ` Jon Masters
2006-03-03 15:25 ` Jeff Dike [this message]

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=20060303152527.GA3536@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=devzero@web.de \
    --cc=linux-kernel@vger.kernel.org \
    /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