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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABb+yY0geOHVz16PsZMbk2OWuJ91Cg-EBvKWfosxe7V5c-EBkQ@mail.gmail.com>
Date: Sun, 29 Sep 2024 17:21:36 -0500
From: Jassi Brar <jassisinghbrar@...il.com>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: axboe@...nel.dk, gost.dev@...sung.com, kernel@...kajraghav.com, 
	linux-block@...r.kernel.org, linux-kernel@...r.kernel.org, minchan@...nel.org, 
	p.raghav@...sung.com
Subject: Re: [PATCH 0/5] Improve zram writeback performance

On Wed, Sep 25, 2024 at 11:34 PM Sergey Senozhatsky
<senozhatsky@...omium.org> wrote:
>
> On (24/09/25 10:53), Jassi Brar wrote:
> > Hi Sergey, Hi Minchan,
> >
> > >> Gentle ping Minchan and Sergey.
> > >
> > May I please know where we are with the rework? Is there somewhere I
> > could look up the compressed-writeback work-in-progress code?
>
> There is no code for that nor any progress that can be shared,
> as far as I'm concerned.
>
> The most recent writeback-related patch series (WIP) reworks
> how writeback and re-compression select target slots for
> post-processing [1]
>
Thanks for the update, Sergey,

Minchan, if you are not pursuing that patchset anymore, is it possible
to share the last version you had? That could avoid re-writing from
scratch and, more importantly, straying too far from your preferred
implementation.

Thanks
Jassi

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ