[PATCH 3/5] nvme_fcloop: split job struct from transport for req_release

Sagi Grimberg sagi at grimberg.me
Thu Apr 20 04:06:39 PDT 2017



On 24/03/17 06:43, jsmart2021 at gmail.com wrote:
> From: James Smart <jsmart2021 at gmail.com>
>
> Current design has the fcloop job struct, used for both initiator and
> target processing, allocated as part of the initiator request structure.
> On aborts, the initiator side (based on the request) may terminate, yet
> the target side wants to continue processing. the target side can't do
> that if the initiator side goes away.

Isn't refcount an easier way to go?

otherwise looks fine,

Reviewed-by: Sagi Grimberg <sagi at grimbeg.me>



More information about the Linux-nvme mailing list