linux-kernel - Re: [PATCH] zram: support a page writeback

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: <20201016202926.GB1976566@google.com>
Date:   Fri, 16 Oct 2020 13:29:26 -0700
From:   Minchan Kim <minchan@...nel.org>
To:     Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>, rajekumar@...gle.com,
        amosbianchi@...gle.com, joaodias@...gle.com
Subject: Re: [PATCH] zram: support a page writeback

Hi Sergey,

On Fri, Oct 16, 2020 at 09:25:47AM +0900, Sergey Senozhatsky wrote:
> On (20/10/12 00:14), Minchan Kim wrote:
> >  
> >  With the command, zram writeback idle pages from memory to the storage.
> >  
> > +If admin want to write a specific page in zram device to backing device,
> > +they could write the page index into the interface.
> > +
> > +	echo 1251 > /sys/block/zramX/writeback
> > +
> 
> May be we can make it more explicit?
> 
> 	echo "page_index=123" > /sys/block/zramX/writeback
> 
> Just in case of future extensions. E.g. someone might want to
> have something like
> 
> 	echo "idle_nr=123" > /sys/block/zramX/writeback
> 
> which would write_back 123 idle pages max.
> 
> 	-ss

Make sense. I will use echo "block_index" since page size could be
changed later(e.g., some pages are 4K, some are THP).
I will revise it at next spin.

Thanks, Sergey!