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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAOH5QeCyxtnZ8UYci2XM9hTnDb7KDy+L2RWaG3u_KMEaNzV8Bg@mail.gmail.com>
Date:   Sat, 15 May 2021 23:33:29 +0800
From:   yong w <yongw.pur@...il.com>
To:     linux-kernel@...r.kernel.org, minchan@...nel.org,
        ngupta@...are.org, sergey.senozhatsky.work@...il.com
Subject: How to calculate available memory when zram is used?

How to calculate available memory when zram is used?
Available+Swap free memeory is obviously bigger than I actually can
use, because zram can compress memory by compression algorithm and
zram compressed data will occupy memeory too.
Is there any way to calculate available memory accurately?

I think of a way is to count the compression rate of zram in the
kernel. The available memory  is calculated as follows:
available + swapfree - swapfree * compress ratio
Is it reasonable?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ