From: "Bryn M. Reeves" <bmr@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Matt Coleman <mcoleman@dattobackup.com>, breeves@redhat.com
Subject: Re: dm-loop and kernel 3.x
Date: Wed, 08 Aug 2012 15:46:27 +0100 [thread overview]
Message-ID: <50227BC3.3050002@redhat.com> (raw)
In-Reply-To: <FB767254-0A6B-42BF-92C7-0527F5329F84@dattobackup.com>
On 08/08/2012 03:33 PM, Matt Coleman wrote:
> I just tried (unsuccessfully) to apply the dm-loop patches to kernel
> 3.2.0. dm-bio-list-helpers.patch failed to apply because
Out of interest, what features where you particularly interested in in
dm-loop today? The original motivation was performance and to break the
limit on the maximum number of loop devices (both of which are now
somewhat less of a problem for the main loop driver) so the main benefit
today seems to be to have loopback support as a native dm target
(avoiding the need for two block devices to use loop files).
Regards,
Bryn.
next prev parent reply other threads:[~2012-08-08 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 14:33 dm-loop and kernel 3.x Matt Coleman
2012-08-08 14:42 ` Bryn M. Reeves
2012-08-08 14:46 ` Bryn M. Reeves [this message]
2012-08-08 15:34 ` Matt Coleman
2012-08-08 16:00 ` Bryn M. Reeves
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=50227BC3.3050002@redhat.com \
--to=bmr@redhat.com \
--cc=breeves@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mcoleman@dattobackup.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.