From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-mtd@lists.infradead.org
Subject: Re: New compression method for JFFS2
Date: Tue, 29 Nov 2005 08:02:11 +0100 [thread overview]
Message-ID: <200511290802.11932.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <438B9355.6080603@greyinnovation.com>
> With the crypto stuff being used, is there much of a performance hit?
You don't have to do crypto, you can. If you don't use it, it won't hurt
performance.
Kernel Crypto API is not just crypto (like aes.c, des.c, ...), but also about
compression (compress.c, deflate.c, ...) and HMACs (md5.c, sha1.c, ...).
prev parent reply other threads:[~2005-11-29 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 11:14 New compression method for JFFS2 Ferenc Havasi
2005-11-25 11:47 ` Holger Schurig
2005-11-25 15:00 ` Ferenc Havasi
2005-11-28 23:31 ` Tehn Yit Chin
2005-11-29 7:02 ` Holger Schurig [this message]
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=200511290802.11932.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=linux-mtd@lists.infradead.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