All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan E Brassow <jbrassow@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: device mapper integrated loops - and one more year !
Date: Mon, 9 Oct 2006 17:36:40 -0500	[thread overview]
Message-ID: <950bd3ad1504b8fb03e73b6236a808bc@redhat.com> (raw)
In-Reply-To: <2c53b31c0610060238nef13171ma6f4a42ba755c3b0@mail.gmail.com>


On Oct 6, 2006, at 4:38 AM, David Guyon Martin wrote:

> On Thu, 5 Oct 2006 20:40:05 +0100 Alasdair G Kergon wrote:
>
>> Something like:
>>   
>> http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/ 
>> editing/dm-loop.patch
>> now perhaps?
>
>> (And there are patches for dmsetup to become a drop-in losetup  
>> replacement.)
>
> Yes! This patch add a new file to the kernel tree, dm-loop.c:
> "This implements a loopback target for device mapper allowing a regular
> file to be treated as a block device."
>
> Great !!! At last :)
> It seems this dm-loop is quite new, less than a month...
> As I understand it I need kernel 2.6.18-rc7 to use it, right ?
>
> I really thank you a lot for your quick answer and link.
>
> Does anyone has yet a feedback about this dm-loop ?
>

I know Heinz Mauelshagen has been looking at it and already has some  
performance improvements.  Perhaps he'll post the updated patches soon.

  brassow

  reply	other threads:[~2006-10-09 22:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06  9:38 device mapper integrated loops - and one more year ! David Guyon Martin
2006-10-09 22:36 ` Jonathan E Brassow [this message]
2006-10-10 18:37   ` Heinz Mauelshagen
2006-10-10 20:11     ` David Guyon Martin
  -- strict thread matches above, loose matches on Subject: below --
2007-01-20 14:57 devzero
2007-01-22  9:43 ` Bryn M. Reeves
2006-11-19 11:30 devzero
2006-10-05 14:26 David Guyon Martin
2006-10-05 19:40 ` Alasdair G Kergon

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=950bd3ad1504b8fb03e73b6236a808bc@redhat.com \
    --to=jbrassow@redhat.com \
    --cc=dm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.