linux-kernel - Re: [RFC][PATCH v3 0/7] introduce automatic pool compaction

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 18 Jun 2015 21:17:46 +0900
From:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:	Minchan Kim <minchan@...nel.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Subject: Re: [RFC][PATCH v3 0/7] introduce automatic pool compaction

Minchan, FYI,

I re-done the test (untouched almost_empty waterline).


		Kernel log
test started [  788.064886]
test ended   [ 4025.914190]

test (doing `cp' in parallel):
(a) for i in {1..X}; do cp -R ~/git .; sync; rm -fr git/; done

# compiled kernel, with object files. 2.2G
(b) for i in {1..X}; do cp -R ~/linux/ .; sync; rm -fr linux/; done

(c) for i in {1..X}; do cp -R ~/glibc/ .; sync; rm -fr glibc/; done


Minimal si_meminfo(&si)->si.freeram observed on the system was: 6390


cat /sys/block/zram0/stat
   31253        0   250024      316 12281689        0 98253512   141263        0   141590   141763

cat /sys/block/zram0/mm_stat
3183374336 2105262569 2140762112        0 2821394432     1864   358173


The results are:

compaction nr:2335 (full:953 part:60956)

ratio: 0.01539   (~1.53% of classes were fully compacted)


More or less same numbers.


	-ss
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/