linux-kernel - Re: [PATCH 00/20] LightNVM: pblk patches for 4.13

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: <20170626222920.GA9175@kernel.dk>
Date:   Mon, 26 Jun 2017 16:29:21 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Javier González <jg@...htnvm.io>
Cc:     mb@...htnvm.io, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Javier González <javier@...xlabs.com>
Subject: Re: [PATCH 00/20] LightNVM: pblk patches for 4.13

On Mon, Jun 26 2017, Javier González wrote:
> Hi Matias,
> 
> Here you have the pblk patchset for this window.
> 
> Apart from small fixes for LightNVM core and pblk, there are three
> relevant changes:
> 
>  - Metadata for each line is no longer issued on a separate workqueue,
>    but instead, all I/Os are scheduled on the write thread. This allows
>    to have more control over LUN collisions. The result is that we can
>    use the full bandwidth of the device for user data. In the 4.12 pblk,
>    we use ~25% of the bandwidth for metadata.
> 
>  - The rate-limiter and GC have been tuned to keep the GC writer busy.
>    Also, capacity per line is guaranteed for GC I/O as we reach
>    capacity.
> 
>  - We have now a FTL state machine. This allows to fail gracefully to
>    user space in case of irrecoverable errors. This state machine will
>    be the base for the pblk's FTL log.
> 
> The patches apply into your for-4.13/core. You can also find them in:

Nope, they do not. Patch #7 fails, because it's not on top of the
bio_set changes that went in a week or two ago. I hand applied that one,
didn't find issues with the rest.

But please remember to ensure that it applies on top of the current
branch.

-- 
Jens Axboe