From: krichel@openlib.org (Thomas Krichel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: zswap compressors
Date: Tue, 26 Nov 2013 15:35:48 +0000 [thread overview]
Message-ID: <20131126153548.GA23389@openlib.org> (raw)
Hi,
I have two issues with zswap.
I am running 3.11.0-13-generic #20~precise2-Ubuntu. The zswap doc
says that I can run a custom compessor and suggests, as an example
in the doc to use, for example, zswap.compressor=deflate as a kernel
option. But when I do that dmesg says "zswap: deflate compressor not
available" and send me back to the default lzo compressor. Trying
lz4 gets the same note. Is this a bug or a feature, and where should
this be reported to?
I wonder why the default compressor is lzo. I understand that,
roughly, lz4 would achieve roughly the same compression and takes
roughly the same effort to compress, but decompresses much
faster. If my understanding is correct, a compressed page is likely
to be decompressed several times while it stays in the pool. I
therefore suspect that lz4 it would be a better compressor for zswap
than lzo. Am I way off base here?
--
Cheers,
Thomas Krichel http://openlib.org/home/krichel
skype:thomaskrichel
reply other threads:[~2013-11-26 15:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131126153548.GA23389@openlib.org \
--to=krichel@openlib.org \
--cc=kernelnewbies@lists.kernelnewbies.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).