From: devzero@web.de
To: Laurent.Vivier@bull.net
Cc: breeves@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][v2] Modify loop device to be able to manage partitions
Date: Fri, 07 Mar 2008 21:34:51 +0100 [thread overview]
Message-ID: <187794188@web.de> (raw)
>Of course, the same behavior can be done using kpartx on a loop device,
>but modifying loop avoids to stack several layers of block device (loop +
>device mapper), this is a very light modification (40% of modifications
>are to manage the new parameter).
iirc, patches like this have been submitted more than once.
i remember i have seen one floating around years ago.
aside from the fact that using partitions on loop devices is useful - if
we had dm-loop (http://sources.redhat.com/lvm2/wiki/DMLoop) in mainline -
would using kpartx with that also mean stacking 2 layers of block device ?
personally, i like the kpartx approach. afaik, it`s working good.
i also like dm-loop, because i think that mapping of files to blockdevices
belongs into an appropriate subsystem like device-mapper.
maybe some of the dm folks know better or have some real arguments - so i`m
adding bryn reeves here. (just noticed that dm-loop disappeared from -mm due
to removal of some api change - so it`s a good chance to bring it back into
discussion) ;)
regards
roland
_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220
reply other threads:[~2008-03-07 20:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=187794188@web.de \
--to=devzero@web.de \
--cc=Laurent.Vivier@bull.net \
--cc=breeves@redhat.com \
--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 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.