linux-kernel - Re: [PATCH] zram: modernize writeback interface

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

Message-ID: <awuyw4jfm2nwxxunchaxazc27m6gqkcyn7zx4gkin7fqg3ogrc@uq55swn7atrx>
Date: Wed, 26 Mar 2025 17:45:56 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Richard Chang <richardycc@...gle.com>
Cc: Minchan Kim <minchan@...nel.org>, 
	Andrew Morton <akpm@...ux-foundation.org>, Brian Geffon <bgeffon@...gle.com>, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org, Sergey Senozhatsky <senozhatsky@...omium.org>
Subject: Re: [PATCH] zram: modernize writeback interface

On (25/03/26 17:15), Sergey Senozhatsky wrote:
> On (25/03/26 15:07), Richard Chang wrote:
> [..]
> > Another alternative thought, how about page_index supporting both
> > single instance and ranges?
> > The key is shorter and the parser is relatively simpler.
> > Eg: page_index=500 page_index=10000-10001
> 
> I probably can look into it.

Can't say I really like that "index" will mean both index and
a range of indexes.  But let me think more.