From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] Fix compression ratio calculation in zram01
Date: Mon, 4 Nov 2019 16:16:49 +0100 [thread overview]
Message-ID: <20191104151647.GA15477@dell5510> (raw)
In-Reply-To: <20191104125228.17173-2-mdoucha@suse.cz>
Hi Martin,
> zram01 uses `free -m` to measure zram memory usage. The results are nonsense
> because they are polluted by all running processes on the system.
> Use /sys/block/zram<id>/mm_stat to measure memory usage instead. The file is
> available since kernel 4.1.
+1 even older kernels won't be covered.
Thanks!
...
> --- a/testcases/kernel/device-drivers/zram/zram01.sh
> zram_fill_fs()
> {
> - tst_test_cmds awk bc dd free
> - local mem_free0=$(free -m | awk 'NR==2 {print $4}')
> + tst_test_cmds awk bc dd
> for i in $(seq 0 $(($dev_num - 1))); do
> tst_resm TINFO "fill zram$i..."
> @@ -75,29 +74,26 @@ zram_fill_fs()
> tst_brkm TBROK "cannot fill zram"
> fi
> tst_resm TINFO "zram$i can be filled with '$b' KB"
> - done
> -
> - local mem_free1=$(free -m | awk 'NR==2 {print $4}')
> - local used_mem=$(($mem_free0 - $mem_free1))
> -
> - local total_size=0
> - for sm in $zram_sizes; do
> - local s=$(echo $sm | sed 's/M//')
> - total_size=$(($total_size + $s))
> - done
> - [ $used_mem -eq 0 ] && tst_brkm TBROK "no memory used by zram"
> + if [ ! -f "/sys/block/zram$i/mm_stat" ]; then
> + if [ $i -eq 0 ]; then
> + tst_resm TCONF "zram compression ratio test requires zram mm_stat sysfs file"
I wonder if /sys/block/zram0/mm_stat is missing whether it can be on any other
zram<id>. Is it it's presence file system specific? Shouldn't we just quit whole
test wit tst_brk TCONF.
Kind regards,
Petr
next prev parent reply other threads:[~2019-11-04 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 12:52 [LTP] [PATCH 0/1] Fix zram01.sh Martin Doucha
2019-11-04 12:52 ` [LTP] [PATCH 1/1] Fix compression ratio calculation in zram01 Martin Doucha
2019-11-04 15:16 ` Petr Vorel [this message]
2019-11-04 15:51 ` Martin Doucha
2019-11-05 8:23 ` Petr Vorel
2019-11-05 8:46 ` Martin Doucha
2019-11-05 9:03 ` [LTP] [PATCH v2 0/1] " Martin Doucha
2019-11-05 9:03 ` [LTP] [PATCH v2 1/1] " Martin Doucha
2019-11-08 15:29 ` Cyril Hrubis
2019-11-08 15:31 ` Martin Doucha
2019-11-08 15:49 ` Cyril Hrubis
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=20191104151647.GA15477@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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