On Wed, 24 July 2013 17:03:53 -0400, Dhaval Giani wrote: > > I am posting this series early in its development phase to solicit some > feedback. At this state, a good description of the format would be nice. > We are implementing transparent decompression with a focus on ext4. One > of the main usecases is that of Firefox on Android. Currently libxul.so > is compressed and it is loaded into memory by a custom linker on > demand. With the use of transparent decompression, we can make do > without the custom linker. More details (i.e. code) about the linker can > be found at https://github.com/glandium/faulty.lib It is not quite clear what you want to achieve here. One approach is to create an empty file, chattr it to enable compression, then write uncompressed data to it. Nothing in userspace will ever know the file is compressed, unless you explicitly call lsattr. If you want to follow some other approach where userspace has one interface to write the compressed data to a file and some other interface to read the file uncompressed, you are likely in a world of pain. Assuming you use the chattr approach, that pretty much comes down to adding compression support to ext4. There have been old patches for ext2 around that never got merged. Reading up on the problems encountered by those patches might be instructive. Jörn -- I've never met a human being who would want to read 17,000 pages of documentation, and if there was, I'd kill him to get him out of the gene pool. -- Joseph Costello -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
