public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: Or Gerlitz <or.gerlitz@gmail.com>, Sagi Grimberg <sagig@mellanox.com>
Cc: target-devel <target-devel@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	"oren@mellanox.com" <oren@mellanox.com>
Subject: Re: [PATCH 09/11] IB/isert: Accept RDMA_WRITE completions
Date: Sun, 12 Jan 2014 14:32:41 +0200	[thread overview]
Message-ID: <52D28B69.6010304@dev.mellanox.co.il> (raw)
In-Reply-To: <CAJZOPZKAH6+4XPv-ua13C5skGYZHXB=tnOFT-7FSNZ5SXKhZMA@mail.gmail.com>

On 1/11/2014 11:14 PM, Or Gerlitz wrote:
> On Thu, Jan 9, 2014 at 6:40 PM, Sagi Grimberg <sagig@mellanox.com> wrote:
>> In case of protected transactions, we will need to check the
>> protection status of the transaction before sending SCSI response.
>> So be ready for RDMA_WRITE completions. currently we don't ask
>> for these completions, but for T10-PI we will.
>> @@ -1721,9 +1735,9 @@ __isert_send_completion(struct iser_tx_desc *tx_desc,
>>                                            isert_conn, ib_dev);
>>                  break;
>>          case ISER_IB_RDMA_WRITE:
>> -               pr_err("isert_send_completion: Got ISER_IB_RDMA_WRITE\n");
>> -               dump_stack();
>> -               break;
>> +               pr_debug("isert_send_completion: Got ISER_IB_RDMA_WRITE\n");
>> +               atomic_dec(&isert_conn->post_send_buf_count);
>> +               isert_completion_rdma_write(tx_desc, isert_cmd);
> are we doing fall through here? why?

Ohhhh, somehow i missed it in squash... Will fix, Thanks!

>>          case ISER_IB_RDMA_READ:
>>                  pr_debug("isert_send_completion: Got ISER_IB_RDMA_READ:\n");
>

  reply	other threads:[~2014-01-12 12:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 16:40 [PATCH 00/11] iSER target initial support for T10-DIF offload Sagi Grimberg
2014-01-09 16:40 ` [PATCH 01/11] Target/core: Fixes for isert compilation Sagi Grimberg
2014-01-09 16:40 ` [PATCH 04/11] IB/isert: Move fastreg descriptor creation to a function Sagi Grimberg
     [not found]   ` <1389285658-7037-5-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-01-13 19:45     ` Nicholas A. Bellinger
2014-01-09 16:40 ` [PATCH 06/11] IB/isert: Initialize T10-PI resources Sagi Grimberg
2014-01-11 21:09   ` Or Gerlitz
2014-01-12 12:41     ` Sagi Grimberg
2014-01-12 14:12       ` Or Gerlitz
2014-01-09 16:40 ` [PATCH 07/11] IB/isert: pass scatterlist instead of cmd to fast_reg_mr routine Sagi Grimberg
2014-01-13 19:45   ` Nicholas A. Bellinger
     [not found] ` <1389285658-7037-1-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-01-09 16:40   ` [PATCH 02/11] IB/isert: seperate connection protection domains and dma MRs Sagi Grimberg
2014-01-13 19:44     ` Nicholas A. Bellinger
2014-01-09 16:40   ` [PATCH 03/11] IB/isert: Avoid frwr notation, user fastreg Sagi Grimberg
2014-01-13 19:44     ` Nicholas A. Bellinger
2014-01-09 16:40   ` [PATCH 05/11] Target/iscsi: Add T10-PI indication for iscsi_portal_group Sagi Grimberg
2014-01-09 16:40   ` [PATCH 08/11] IB/isert: pass mr and frpl to isert_fast_reg_mr routine Sagi Grimberg
2014-01-09 16:40 ` [PATCH 09/11] IB/isert: Accept RDMA_WRITE completions Sagi Grimberg
2014-01-11 21:14   ` Or Gerlitz
2014-01-12 12:32     ` Sagi Grimberg [this message]
2014-01-09 16:40 ` [PATCH 10/11] IB/isert: Support T10-PI protected transactions Sagi Grimberg
2014-01-09 16:40 ` [PATCH 11/11] Target/configfs: Expose iSCSI network portal group T10-PI support 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=52D28B69.6010304@dev.mellanox.co.il \
    --to=sagig@dev.mellanox.co.il \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=nab@linux-iscsi.org \
    --cc=or.gerlitz@gmail.com \
    --cc=oren@mellanox.com \
    --cc=sagig@mellanox.com \
    --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