From: Tomas M <tomas@slax.org>
To: linux-kernel@vger.kernel.org
Subject: Re: max_loop limit
Date: Fri, 23 Mar 2007 09:59:33 +0100 [thread overview]
Message-ID: <460396F5.5020509@slax.org> (raw)
In-Reply-To: <1696002332@web.de>
> wondering that here are 13 postings about loopdevice limitation, but
> nobody giving any comment about dm-loop (
> http://sources.redhat.com/lvm2/wiki/DMLoop ), which is a solution for
> this problem ......
If I understand it correctly, I would need 'dm' in kernel (or module)
and moreover I would need some userspace utilities/binaries.
> It can be used as a 1:1 replacement for classic loop and
> should (?) probably be ready for mainline in the not too far future.
So it is not in Kernel?
With current loop, people would need kernel patch and *no* userspace
utilities.
With dm-loop, people would need kernel patch *and* userspace utilities.
So, from my point of view, it would be better to fix/enhance Linux's loop.
Tomas M
slax.org
next prev parent reply other threads:[~2007-03-23 8:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 23:23 max_loop limit devzero
2007-03-23 8:59 ` Tomas M [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-22 23:37 roland
2007-03-29 14:20 ` Bill Davidsen
2007-03-22 13:53 devzero
2007-03-22 7:57 Tomas M
2007-03-22 11:00 ` markus reichelt
2007-03-22 11:37 ` Tomas M
2007-03-22 13:42 ` Eric Dumazet
2007-03-22 13:42 ` Jens Axboe
2007-03-22 13:52 ` Eric Dumazet
2007-03-22 13:54 ` Jens Axboe
2007-03-22 14:11 ` William Lee Irwin III
2007-03-22 15:22 ` Arjan van de Ven
2007-03-22 16:09 ` Pádraig Brady
2007-03-28 23:34 ` Karel Zak
2007-03-22 14:33 ` Al Viro
2007-03-22 19:51 ` Olivier Galibert
2007-03-22 14:25 ` Tomas M
2007-03-23 1:34 ` Jan Engelhardt
2007-03-29 14:16 ` Bill Davidsen
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=460396F5.5020509@slax.org \
--to=tomas@slax.org \
--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.