From: Mike Fedyk <mfedyk@matchmail.com>
To: Luca Barbato <lu_zero@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcloop: compressed loopback support for 2.6
Date: Mon, 19 Jan 2004 16:23:38 -0800 [thread overview]
Message-ID: <20040120002338.GV8664@srv-lnx2600.matchmail.com> (raw)
In-Reply-To: <400C6AA2.4000307@gentoo.org>
> >On Tue, Jan 20, 2004 at 12:15:24AM +0100, Luca Barbato wrote:
> >>gcloop isn't file format compatible with the old cloop-0.68 fileformat
> >>since I had to use in a different way the index and I prefer ucl instead
> >>of zlib.
> Mike Fedyk wrote:
> >Maybe you can merge ucl into cloop 2.x, and support both (one compression
On Tue, Jan 20, 2004 at 12:39:14AM +0100, Luca Barbato wrote:
> >scheme per image, of course) in the same codebase?
> gcloop supports arbitrary compressor you just have to make the cryptoapi
> module of it,
That's good.
> and obviously change the userspace tools, the only
Hmm, so I presume that gcloop has its own userspace utilities...
> restraint is the file format, the changes I made are due the need to
> avoid high penality on uncompressible blocks
Interesting.
> , with some effort I can
> make the parser support all the formats (gcloop, cloop-0.68,
> cloop-1.0/2.0) but would enlarge the code a bit or make it slower.
It would be good to have all of these competing formats handled, dicesions
on which format(s) should be used for future versions before it's integrated
into mainline.
> >
> >Has cloop been ported to 2.6?
> >
> not that I know.
Boooo, bad knoppix! ;)
prev parent reply other threads:[~2004-01-20 0:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 16:21 cryptoloop extended for compressors Luca Barbato
2004-01-19 16:29 ` gcloop: compressed loopback support for 2.6 Luca Barbato
2004-01-19 16:41 ` Mike Fedyk
2004-01-19 23:15 ` Luca Barbato
2004-01-19 23:25 ` Mike Fedyk
[not found] ` <400C6AA2.4000307@gentoo.org>
2004-01-20 0:23 ` Mike Fedyk [this message]
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=20040120002338.GV8664@srv-lnx2600.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lu_zero@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®