LZMA compression algorithm in Kernel - any chance to allow it?
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)
Thank you
Tomas M
Quoted 2 lines · Tomas M
If I (or anybody else) submit LZMA code for inclusion in kernel, would you ACCEPT IT ?? (assuming the code looks nice to you)
The bad thing is, they won't tell you before you submitted it. The good thing is, that it may get accepted nevertheless if sent often enough.
Quoted 1 line
The bad thing is, they won't tell you before you submitted it.
By 'they' you mean who?
Who decides what is accepted anyway?
* H. Peter Anvin, President ?
* Jeff Uphoff, Treasurer ?
* Chris Wright, Secretary ?
* Kees Cook, Board Member ?
* Linus Torvalds, Board Member ?
[names quoted from http://kernel.org/nonprofit.html:]
Quoted 2 lines
The good thing is, that it may get accepted nevertheless if sent often enough.
Well that point is very interesting and useful indeed :)
Tomas M
slax.org
Quoted 4 lines · Tomas M
Quoted 1 line
The bad thing is, they won't tell you before you submitted it.
By 'they' you mean who?
Who decides what is accepted anyway?
Major contributors (reviewers, maintainers) do, and ultimately Linus.
You said LZMA is already used by out-of-tree code in the embedded domain. So I suppose a submission of an LZMA implementation should rather be part of a submission of code which actually uses it.
Signature · 3 lines
Stefan Richter -=====-==--- -==- ==-=- http://arcgraph.de/sr/
Quoted 9 lines · Tomas M
Hello.
I can see the 2.6.25 kernel includes LZO compression algorithm in:[*] Cryptographic API
< > LZO compression algorithmAs 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
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Well, I use LZMA particularly in squashfs, which is a replacement for cramfs at all.
Unfortunately even squashfs is not in kernel.
Tomas M
Quoted 14 lines · Pavel Machek
Quoted 9 lines · Tomas M
Hello.
I can see the 2.6.25 kernel includes LZO compression algorithm in:[*] Cryptographic API
< > LZO compression algorithmAs 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
Quoted 3 lines · Tomas M
Well, I use LZMA particularly in squashfs, which is a replacement for cramfs at all.
Unfortunately even squashfs is not in kernel.
That's good enough reason. Push squashfs first, or in same series as lzma.
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Quoted 4 lines · Pavel Machek
Quoted 1 line
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'...?
squashfs if at all.
Quoted 7 lines · Jan Engelhardt
Quoted 3 lines · Pavel Machek
Quoted 1 line
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'...?
squashfs if at all.
Well anything can use lzma or any other compressions, not only squashfs. Squashfs is a great example, where you get 30% smaller filesystems compared to gzip.
Tomas M
Quoted 11 lines · Tomas M
Quoted 7 lines · Jan Engelhardt
Quoted 3 lines · Pavel Machek
Quoted 1 line
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'...?
squashfs if at all.
Well anything can use lzma or any other compressions, not only squashfs. Squashfs is a great example, where you get 30% smaller filesystems compared to gzip.
JFFS2 has an framework for having multiple compression algorithms. Adding LZMA to that wouldn't be difficult either.
josh
Quoted 11 lines · Tomas M
Quoted 7 lines · Jan Engelhardt
Quoted 3 lines · Pavel Machek
Quoted 1 line
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'...?
squashfs if at all.
Well anything can use lzma or any other compressions, not only squashfs. Squashfs is a great example, where you get 30% smaller filesystems compared to gzip.
I rather meant "who would still use cramfs", given that squashfs actually crams more files into the same space.