From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 3/5] nvme_fcloop: split job struct from transport for req_release
Date: Thu, 20 Apr 2017 14:06:39 +0300 [thread overview]
Message-ID: <77336c0d-5c20-b36e-da62-bbab5e96b36f@grimberg.me> (raw)
In-Reply-To: <20170324034321.8719-4-jsmart2021@gmail.com>
On 24/03/17 06:43, jsmart2021@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>
next prev parent reply other threads:[~2017-04-20 11:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 3:43 [PATCH 0/5] nvmet_fc: bug fixes and lldd api mods jsmart2021
2017-03-24 3:43 ` [PATCH 1/5] nvmet_fc: add target feature flags for upcall isr contexts jsmart2021
2017-04-20 10:58 ` Sagi Grimberg
2017-03-24 3:43 ` [PATCH 2/5] nvmet_fc: add req_release to lldd api jsmart2021
2017-04-20 11:02 ` Sagi Grimberg
2017-03-24 3:43 ` [PATCH 3/5] nvme_fcloop: split job struct from transport for req_release jsmart2021
2017-04-20 11:06 ` Sagi Grimberg [this message]
2017-03-24 3:43 ` [PATCH 4/5] nvmet_fc: Rework target side abort handling jsmart2021
2017-04-20 11:15 ` Sagi Grimberg
2017-03-24 3:43 ` [PATCH 5/5] nvmet_fc: add missing reference in add_port jsmart2021
2017-04-20 11:16 ` Sagi Grimberg
2017-04-05 8:05 ` [PATCH 0/5] nvmet_fc: bug fixes and lldd api mods Sagi Grimberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=77336c0d-5c20-b36e-da62-bbab5e96b36f@grimberg.me \
--to=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).