From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Subject: Re: [GIT PULL 00/25] LightNVM updates for 4.16 To: Jens Axboe References: <20180105131621.20808-1-m@bjorling.me> <20180105155054.GB13829@kernel.dk> Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org From: =?UTF-8?Q?Matias_Bj=c3=b8rling?= Message-ID: <83c66c1c-ba27-4cfd-da9e-a57c1f941d47@bjorling.me> Date: Fri, 5 Jan 2018 19:34:41 +0100 MIME-Version: 1.0 In-Reply-To: <20180105155054.GB13829@kernel.dk> Content-Type: text/plain; charset=windows-1252; format=flowed List-ID: On 01/05/2018 04:50 PM, Jens Axboe wrote: > 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. > Thanks Jens. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752451AbeAESep (ORCPT + 1 other); Fri, 5 Jan 2018 13:34:45 -0500 Received: from mail-lf0-f53.google.com ([209.85.215.53]:46115 "EHLO mail-lf0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752214AbeAESeo (ORCPT ); Fri, 5 Jan 2018 13:34:44 -0500 X-Google-Smtp-Source: ACJfBounuIxCxj4BJiekVNWh+kSZ0vzQMb9x1uENMy4RlPt/tfzmx0LAsL1bOCBz5T+a9Z0FwRUOqQ== Subject: Re: [GIT PULL 00/25] LightNVM updates for 4.16 To: Jens Axboe References: <20180105131621.20808-1-m@bjorling.me> <20180105155054.GB13829@kernel.dk> Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org From: =?UTF-8?Q?Matias_Bj=c3=b8rling?= Message-ID: <83c66c1c-ba27-4cfd-da9e-a57c1f941d47@bjorling.me> Date: Fri, 5 Jan 2018 19:34:41 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20180105155054.GB13829@kernel.dk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On 01/05/2018 04:50 PM, Jens Axboe wrote: > 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. > Thanks Jens.