linux-kernel - Re: [GIT PULL 00/25] LightNVM updates for 4.16

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

Date:   Fri, 5 Jan 2018 08:50:55 -0700
From:   Jens Axboe <axboe@...nel.dk>
To:     Matias Bjørling <m@...rling.me>
Cc:     linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL 00/25] LightNVM updates for 4.16

On Fri, Jan 05 2018, Matias Bjørling wrote:
> Hi Jens,
> 
> Here is a couple of patches for 4.16.
> 
> This patchset prepares the lightnvm and pblk source code for the 2.0
> specification release. The specification is close to its final
> revision. After these changes, 2.0 support is a quick drop.
> 
> While adopting 2.0 specification, the rrpc and null_blk
> implementation had to go. rrpc used the deprecated device-side
> table mapping table API for the 1.2 specification, and there are
> no users of it. Similarly, null_blk has not worked with pblk for
> a while.
> 
> Javier and Hans have been hard at work at fixing up bugs in pblk,
> especially concerning synchronization points between user I/O and GC
> I/O. While also fixing bugs that occurred on bringup/bringdown.
> 
> They also added support for iostats and added an option to add
> support for defining the amount of over-provisioning an instance
> should have.

Apart from the minor comment on one of the later patches, looks fine to
me. Applied for 4.16.

-- 
Jens Axboe