From: Tomas M <tomas@slax.org>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: LZMA compression algorithm in Kernel - any chance to allow it?
Date: Fri, 27 Jun 2008 14:14:39 +0200 [thread overview]
Message-ID: <4864D9AF.4030509@slax.org> (raw)
In-Reply-To: <20080626201754.GE9878@ucw.cz>
Well, I use LZMA particularly in squashfs, which is a replacement for cramfs at all.
Unfortunately even squashfs is not in kernel.
Tomas M
Pavel Machek wrote:
> On Thu 2008-06-26 09:56:23, Tomas M wrote:
>> Hello.
>> I can see the 2.6.25 kernel includes LZO compression algorithm in:
>>
>> [*] Cryptographic API
>> < > LZO compression algorithm
>>
>> As far as I could see, there was a strong pressure against putting compression algorithms in kernel. Does this LZO example mean that kernel people are now more open to include other algorithms as well? I'd like to include LZMA algo, which has far better compression ratio then anything else widely used today, and is already used in many small or embeded systems (as external patches to kernel or userspace utilities)
>>
>> If I (or anybody else) submit LZMA code for inclusion in kernel, would you ACCEPT IT ?? (assuming the code looks nice to you)
>
> You need some good reason why lzma should be in kernel... like 'cramfs
> can use it'...?
> Pavel
next prev parent reply other threads:[~2008-06-27 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 7:56 LZMA compression algorithm in Kernel - any chance to allow it? Tomas M
2008-06-26 12:31 ` Jan Engelhardt
2008-06-26 13:37 ` Tomas M
2008-06-26 16:00 ` Stefan Richter
2008-06-26 20:17 ` Pavel Machek
2008-06-27 12:14 ` Tomas M [this message]
2008-06-27 12:20 ` Pavel Machek
2008-06-27 13:32 ` Jan Engelhardt
2008-06-27 14:11 ` Tomas M
2008-06-27 14:15 ` Josh Boyer
2008-07-01 6:37 ` Jan Engelhardt
[not found] <fa.WuwHJZhCHgER6Pu+gn66zdRwVUg@ifi.uio.no>
2008-06-27 1:58 ` Robert Hancock
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=4864D9AF.4030509@slax.org \
--to=tomas@slax.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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