linux-kernel - Re: [PATCH 1/1] zram: better utilization of zram swap space

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20171211015520.GA6479@jagdpanzerIV>
Date:   Mon, 11 Dec 2017 10:55:20 +0900
From:   Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To:     Minchan Kim <minchan@...nel.org>
Cc:     Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
        Gopi Sai Teja <gopi.st@...sung.com>, ngupta@...are.org,
        linux-kernel@...r.kernel.org, v.narang@...sung.com,
        pankaj.m@...sung.com, a.sahrawat@...sung.com,
        prakash.a@...sung.com, himanshu.sh@...sung.com
Subject: Re: [PATCH 1/1] zram: better utilization of zram swap space

On (12/11/17 09:16), Minchan Kim wrote:
[..]
> I agree. zram shouldn't be aware of allocator internal.
> It would be better for zram to use *int zs_max_zpage_size(struct zs_pool *pool)*
> to set up max_zpage_size.
> Let's hide the allocator's detail to the exported function.

Hi Minchan,

cool :)

I'll re-spin the patch [in a day or two]. and then *may be* we can
return to the huge-class watermark proposition. may be there can be
a knob or something of that kind.

	-ss