linux-kernel - what's cooking in zram for 4.2

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]

Date:	Thu, 13 Aug 2015 09:58:12 +0900
From:	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To:	Karel Zak <kzak@...hat.com>
Cc:	Minchan Kim <minchan@...nel.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
	Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
	linux-kernel@...r.kernel.org, util-linux@...r.kernel.org
Subject: what's cooking in zram for 4.2

Hello Karel,

... planned to write this earlier.


zram will see some user-space visible improvements in 4.2 we'd love
to let you know about -- on-demand device creation/removal.

For that purpose we introduce zram control sysfs class, which has two
sysfs attrs:
 - hot_add      -- add a new zram device
 - hot_remove   -- remove a specific (device_id) zram device


-- hot_add sysfs attr is read-only and has only automatic device id
assignment mode.  Read operation performed on this attr creates a
new zram device and returns back its device_id (or error (ret < 0)).

Usage example:
  # add a new zram device
  cat /sys/class/zram-control/hot_add
  2

an example of returning error code (-ENOMEM in this case)

  cat /sys/class/zram-control/hot_add
  cat: /sys/class/zram-control/hot_add: Cannot allocate memory



-- hot_remove is write only and requires a valid zram device_id as
its input parameter:

  # remove a specific zram device
  echo 4 > /sys/class/zram-control/hot_remove


	-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/