> On 1 Mar 2018, at 12.51, Matias Bjørling wrote:
>
> On 03/01/2018 12:02 PM, Javier Gonzalez wrote:
>>> On 1 Mar 2018, at 11.40, Matias Bjørling wrote:
>>>
>>> On 02/28/2018 04:49 PM, Javier González wrote:
The 2.0 spec provides a report chunk log page that can be retrieved
using th
On 03/01/2018 12:02 PM, Javier Gonzalez wrote:
On 1 Mar 2018, at 11.40, Matias Bjørling wrote:
On 02/28/2018 04:49 PM, Javier González wrote:
The 2.0 spec provides a report chunk log page that can be retrieved
using the stangard nvme get log page. This replaces the dedicated
get/put bad block
> On 1 Mar 2018, at 11.40, Matias Bjørling wrote:
>
> On 02/28/2018 04:49 PM, Javier González wrote:
>> The 2.0 spec provides a report chunk log page that can be retrieved
>> using the stangard nvme get log page. This replaces the dedicated
>> get/put bad block table in 1.2.
>> This patch impleme
On 02/28/2018 04:49 PM, Javier González wrote:
The 2.0 spec provides a report chunk log page that can be retrieved
using the stangard nvme get log page. This replaces the dedicated
get/put bad block table in 1.2.
This patch implements the helper functions to allow targets retrieve the
chunk meta
The 2.0 spec provides a report chunk log page that can be retrieved
using the stangard nvme get log page. This replaces the dedicated
get/put bad block table in 1.2.
This patch implements the helper functions to allow targets retrieve the
chunk metadata using get log page. It makes nvme_get_log_ex