From: "Bryn M. Reeves" <breeves@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Re: device mapper integrated loops - and one more year !
Date: Tue, 21 Nov 2006 21:11:37 +0000 [thread overview]
Message-ID: <45636B89.7080407@redhat.com> (raw)
In-Reply-To: <1439173022@web.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
devzero@web.de wrote:
> Hello !
>
> after desparately seeking for a solution to have more than 256 loop
> devices (for a huge cd-rom server), i have recently come across
> dm-loop, which looks very promising (to replace loop.c)
>
> can i have more than 256 devices which this?
Hi Roland,
Yes, dm-loop will support as many loop devices as device-mapper can allow.
> our cd-rom server is going to have more than 256 iso-images soon and
> i need to upgrade to a more recent OS, anyway, so this won`t be a
> problem that dm-loop is so brand new.
>
> but - any timeline for dm-loop mainline inclusion ?
>
> should i wait for 2.6.19 or 2.6.20 ?
There isn't a fixed timeline. We are currently working to improve the
lookup code - the prototype patch uses a linear search which doesn't
scale well for large/fragmented image files. I have some tests running
at the moment and we hope to have something soon - the results so far
are good, it's just a case of selecting between a couple of different
methods.
The changes dm-loop requires in device-mapper core are pretty minor and
have already been merged in 2.6.19, so it's just the dm-loop patch
itself remaining.
> is it already useable with less recent kernels, i.e. can i download
> dm-loop patch and recent dmsetup tool and use with older kernel ?
This should work fine - there are a couple of known issues with the
existing patch, but unless you are using large images (>2G), or have a
severely fragmented filesystem you shouldn't run into these.
I'll see if we can get a revised version of the current patch for wider
testing in the next couple of weeks - let me know if you would be
interested in trying this out.
Thanks,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFFY2uJ6YSQoMYUY94RArTwAJwMmCJbTajxmX6Q/ps545zbgvJJOACg28NP
A+F6CtqcHH0fOG9lq2XQw/8=
=CzES
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-11-21 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 11:30 device mapper integrated loops - and one more year ! devzero
2006-11-21 21:11 ` Bryn M. Reeves [this message]
2006-11-21 21:55 ` Roland PJ
2006-11-21 23:20 ` Bryn M. Reeves
2006-11-22 8:29 ` Roland Paterson-Jones
2006-11-22 21:37 ` Bryn M. Reeves
2006-11-23 11:15 ` Roland Paterson-Jones
-- strict thread matches above, loose matches on Subject: below --
2007-01-20 14:57 devzero
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=45636B89.7080407@redhat.com \
--to=breeves@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.