From: sagi grimberg <sagig@mellanox.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Sagi Grimberg <sagig@dev.mellanox.co.il>
Cc: "Nicholas A. Bellinger" <nab@daterainc.com>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
Quinn Tran <quinn.tran@qlogic.com>,
Giridhar Malavali <giridhar.malavali@qlogic.com>
Subject: Re: [PATCH 7/9] target: Enable WRITE_INSERT emulation in target_execute_cmd
Date: Mon, 7 Apr 2014 11:13:50 +0300 [thread overview]
Message-ID: <53425E3E.3080509@mellanox.com> (raw)
In-Reply-To: <1396858271.19888.9.camel@haakon3.risingtidesystems.com>
On 4/7/2014 11:11 AM, Nicholas A. Bellinger wrote:
>> Looks good to me.
>>
>> Reviewed-by: Sagi Grimberg <sagig@mellanox.com>
>>
>> This is useless though without the code setting this prot_op in
>> sbc_set_prot_op_checks()...
> Not sure I follow.. sbc_set_prot_op_checks() is already setting
> TARGET_PROT_DOUT_INSERT when no protect field in the WRITE CDB has been
> set, eg:
>
> static int
> sbc_set_prot_op_checks(u8 protect, enum target_prot_type prot_type,
> bool is_write, struct se_cmd *cmd)
> {
> if (is_write) {
> cmd->prot_op = protect ? TARGET_PROT_DOUT_PASS :
> TARGET_PROT_DOUT_INSERT;
>
> <SNIP>
> }
> }
>
> Which in-turn is what causes this code to invoke sbc_dif_write_insert
> (now sbc_dif_generate) when the backend supports PI, and the fabric
> itself does not support WRITE_INSERT hw offload.
pphh,
I confused this with DOUT_STRIP/DIN_INSERT.
You can discard.
Sagi.
next prev parent reply other threads:[~2014-04-07 8:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 9:35 [PATCH 0/9] target: Allow fabric to expose PI + add WRITE_INSERT/READ_STRIP Nicholas A. Bellinger
2014-04-03 9:35 ` [PATCH 1/9] target/iblock: Fix double bioset_integrity_free bug Nicholas A. Bellinger
2014-04-07 7:19 ` Sagi Grimberg
2014-04-03 9:35 ` [PATCH 2/9] target: Pass in transport supported PI at session initialization Nicholas A. Bellinger
2014-04-07 7:28 ` Sagi Grimberg
2014-04-07 8:01 ` Nicholas A. Bellinger
2014-04-03 9:35 ` [PATCH 3/9] target/spc: Only expose PI inquiry bits when supported by fabric Nicholas A. Bellinger
2014-04-07 7:30 ` Sagi Grimberg
2014-04-03 9:35 ` [PATCH 4/9] target/spc: Only expose PI mode page " Nicholas A. Bellinger
2014-04-07 7:31 ` Sagi Grimberg
2014-04-03 9:35 ` [PATCH 5/9] target/sbc: Only expose PI read_cap16 " Nicholas A. Bellinger
2014-04-07 7:32 ` Sagi Grimberg
2014-04-03 9:35 ` [PATCH 6/9] target/sbc: Add sbc_dif_write_insert software emulation Nicholas A. Bellinger
2014-04-07 7:36 ` Sagi Grimberg
2014-04-07 8:07 ` Nicholas A. Bellinger
2014-04-03 9:35 ` [PATCH 7/9] target: Enable WRITE_INSERT emulation in target_execute_cmd Nicholas A. Bellinger
2014-04-07 7:39 ` Sagi Grimberg
2014-04-07 8:11 ` Nicholas A. Bellinger
2014-04-07 8:13 ` sagi grimberg [this message]
2014-04-03 9:35 ` [PATCH 8/9] target/sbc: Add sbc_dif_read_strip software emulation Nicholas A. Bellinger
2014-04-07 7:44 ` Sagi Grimberg
2014-04-03 9:35 ` [PATCH 9/9] target: Enable READ_STRIP emulation in target_complete_ok_work Nicholas A. Bellinger
2014-04-07 7:49 ` Sagi Grimberg
2014-04-07 8:15 ` Nicholas A. Bellinger
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=53425E3E.3080509@mellanox.com \
--to=sagig@mellanox.com \
--cc=giridhar.malavali@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nab@daterainc.com \
--cc=nab@linux-iscsi.org \
--cc=ogerlitz@mellanox.com \
--cc=quinn.tran@qlogic.com \
--cc=sagig@dev.mellanox.co.il \
--cc=target-devel@vger.kernel.org \
/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