[lkml]   [2001]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: libz, libbz2, ramfs and cramfs
Followup to:  <>
By author: "Matt D. Robinson" <>
In newsgroup:
> >
> > The -ac tree is moving to a single copy of zlib, in fs/inflate_fs. It
> > is currently used by cramfs and zisofs. jffs2 in the -ac tree still
> > uses its own copy of zlib and should be converted.
> Any plans to fix this for the Linus tree? Also, why place this in fs?
> Shouldn't this be around for PPP along with other things that
> can use it (like LKCD)?

PPP uses a nonstandard deviant of zlib, or *so I've been told*, so
that one is out.

The reason it's in fs is because I wasn't feeling sure that the memory
management as implemented is adequate for non-fs-related
applications. I might change that, though, but I wanted to move
somewhat slowly.

Memory management in zlib is nontrivial. If you port the user-space
zlib the "obvious" way to kernel space, you get memory management that
is completely unacceptable to a filesystem application -- too easy to
get random errors due to memory allocation failures.

A major problem is that the module name "deflate" is used by PPP,
despite it being a nonstandard format...

<> at work, <> in private!
"Unix gives you enough rope to shoot yourself in the foot." <>
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:08    [W:0.053 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site