From: "Etienne Lorrain" <etienne_lorrain@yahoo.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] 2.5.73 zlib #1 memmove
Date: Wed, 2 Jul 2003 11:27:07 +0200 (CEST) [thread overview]
Message-ID: <20030702092707.24387.qmail@web11805.mail.yahoo.com> (raw)
Hi,
I do not know if you are interrested, but I already did
a lot work on zlib/gzlib in Gujin:
http://gujin.sourceforge.net/
There is a near complete rewrite of zlib, even removing the
32Kb window stuff. Unlike zlib, it is only licenced as GPL, and only
tested on i386, in fact 32 bit processors. An unusual CRC32 function
is also available, optimised to i386 instructions but without a table
to reduce the data cache page misses and code size.
Have a look at gzcopy.c:
gzcopy -t infile.gz -> test the content of the file (-t0 for quite).
The kind of testing done is in Makefile:
testgzlib: gzcopy
find /mnt/cdrom/ -name "*.tgz" -o -name "*.gz" \
-exec ./gzcopy -t {} \; 2>&1 | tee log
I did it on multi CDROMs collection like ftp.cdrom.com , it checks
all files CRC32 - the only failure were unreadable files on the device
and file not compressed by GZIP (GZIP can decompress .Z and .ZIP files)
even if someone changed their name to *.gz
My aim there was code size reduction (4-5 Kbytes of code total).
It does compile and work with GCC aliasing optimisation.
Cheers,
Etienne.
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
next reply other threads:[~2003-07-02 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 9:27 Etienne Lorrain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-01 15:45 [PATCH RFC] 2.5.73 zlib #1 memmove Jörn Engel
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=20030702092707.24387.qmail@web11805.mail.yahoo.com \
--to=etienne_lorrain@yahoo.fr \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).