From: Andrew Randrianasulu <randrianasulu@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Zstd and zram - not finished?
Date: Sat, 10 Feb 2018 02:13:51 +0300 [thread overview]
Message-ID: <201802100213.52152.randrianasulu@gmail.com> (raw)
Hello, I was trying to test zstd compression for zram devices with kernel 4.15
But to my surprize I found zstd comressor missing from list of compression
algos.
I found out this patch or equivalent was still missing in 4.15 and missing in
4.16 as it nearing -rc1:
https://lkml.org/lkml/2017/8/4/582
[PATCH v4 5/5] crypto: Add zstd support
After manually applying this patch I can see
cat /sys/class/block/zram0/comp_algorithm
[lzo] lz4 lz4hc 842 zstd
and can change algo to zstd
If I try and mkfs.ext2 this device (with size, say, ~1Gb) - I can uncompress
nearly full kernel tree into it (I first run out of inodes, tons of small files
for such small "disk", re-run mkfs with specified number of inodes, around 100
000, worked). But 1Gb device probably was visible size of device, not amount of
memory it consumes..So, I run mkfs.btrfs over /dev/zram0 with zstd compression.
This give me ~1Gb sized device able to keep full kernel tree, and compile it ,
too. So, I assume it worked ....
reply other threads:[~2018-02-09 23:24 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=201802100213.52152.randrianasulu@gmail.com \
--to=randrianasulu@gmail.com \
--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).