[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191025002050.GC28602@redsun51.ssa.fujisawa.hgst.com>
Date: Fri, 25 Oct 2019 09:20:50 +0900
From: Keith Busch <kbusch@...nel.org>
To: Logan Gunthorpe <logang@...tatee.com>
Cc: linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@....com>,
Max Gurtovoy <maxg@...lanox.com>,
Stephen Bates <sbates@...thlin.com>
Subject: Re: [PATCH 0/7] Remove data_len field from the nvmet_req struct
On Wed, Oct 23, 2019 at 10:35:38AM -0600, Logan Gunthorpe wrote:
> Hi,
>
> This patchset is a cleanup in preparation for the passthru patchset.
> The aim is to remove the data_len field in the nvmet_req struct and
> instead just check the length is appropriate inside the execute
> handlers. This is more appropriate for passthru which may have
> commands with unknown lengths (like Vendor Specific Commands).
> It's also in improvement seeing it can often be confusing when
> it's best to use the data_len field over the transfer_len field.
> The first two patches in this series remove some questionable uses
> of the data_len field in nvmt-tcp
>
> Most of this patchset was extracted from a draft patch from
> Christoph[1].
>
> The series is based on v5.4-rc4 and a git branch is available here:
>
> https://github.com/sbates130272/linux-p2pmem/branches nvmet_data_len
>
> Logan
Thanks, applied to nvme-5.5 with the requested author attribution.
Powered by blists - more mailing lists