All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagi@grimberg.me>
To: Max Gurtovoy <maxg@mellanox.com>,
	Sagi Grimberg <sagi@lightbitslabs.com>,
	linux-nvme@lists.infradead.org
Cc: linux-block@vger.kernel.org, netdev@vger.kernel.org,
	Keith Busch <keith.busch@intel.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 05/11] nvmet: Add install_queue callout
Date: Mon, 19 Nov 2018 13:21:58 -0800	[thread overview]
Message-ID: <98230184-074a-84cf-3aa5-8ad30f2b5339@grimberg.me> (raw)
In-Reply-To: <af370da9-3d56-e1a8-27db-c0a8e9291417@mellanox.com>


>> diff --git a/drivers/nvme/target/fabrics-cmd.c 
>> b/drivers/nvme/target/fabrics-cmd.c
>> index 1f05d8507e35..a84668e8939c 100644
>> --- a/drivers/nvme/target/fabrics-cmd.c
>> +++ b/drivers/nvme/target/fabrics-cmd.c
>> @@ -117,6 +117,15 @@ static u16 nvmet_install_queue(struct nvmet_ctrl 
>> *ctrl, struct nvmet_req *req)
>>       nvmet_sq_setup(ctrl, req->sq, qid, sqsize + 1,
>>               !!(c->cattr & NVME_CONNECT_DISABLE_SQFLOW));
> 
> what is your code base ? does SQFLOW must for TCP ?

Not really, just happens to sit on top..

>> +    if (ctrl->ops->install_queue) {
>> +        int ret = ctrl->ops->install_queue(req->sq);
>> +        if (ret) {
>> +            pr_err("failed to install queue %d cntlid %d ret %d\n",
>> +                qid, ret, ctrl->cntlid);
>> +            return NVME_SC_CONNECT_INVALID_PARAM | NVME_SC_DNR;
> 
> I'm not sure regarding the INVALID_PARAM rc.
> 
> maybe use NVME_SC_INTERNAL ?

You're right, perhaps we should propagate ->install_queue() status.

WARNING: multiple messages have this Message-ID (diff)
From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 05/11] nvmet: Add install_queue callout
Date: Mon, 19 Nov 2018 13:21:58 -0800	[thread overview]
Message-ID: <98230184-074a-84cf-3aa5-8ad30f2b5339@grimberg.me> (raw)
In-Reply-To: <af370da9-3d56-e1a8-27db-c0a8e9291417@mellanox.com>


>> diff --git a/drivers/nvme/target/fabrics-cmd.c 
>> b/drivers/nvme/target/fabrics-cmd.c
>> index 1f05d8507e35..a84668e8939c 100644
>> --- a/drivers/nvme/target/fabrics-cmd.c
>> +++ b/drivers/nvme/target/fabrics-cmd.c
>> @@ -117,6 +117,15 @@ static u16 nvmet_install_queue(struct nvmet_ctrl 
>> *ctrl, struct nvmet_req *req)
>> ????? nvmet_sq_setup(ctrl, req->sq, qid, sqsize + 1,
>> ????????????? !!(c->cattr & NVME_CONNECT_DISABLE_SQFLOW));
> 
> what is your code base ? does SQFLOW must for TCP ?

Not really, just happens to sit on top..

>> +??? if (ctrl->ops->install_queue) {
>> +??????? int ret = ctrl->ops->install_queue(req->sq);
>> +??????? if (ret) {
>> +??????????? pr_err("failed to install queue %d cntlid %d ret %d\n",
>> +??????????????? qid, ret, ctrl->cntlid);
>> +??????????? return NVME_SC_CONNECT_INVALID_PARAM | NVME_SC_DNR;
> 
> I'm not sure regarding the INVALID_PARAM rc.
> 
> maybe use NVME_SC_INTERNAL ?

You're right, perhaps we should propagate ->install_queue() status.

  reply	other threads:[~2018-11-19 21:22 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15 17:16 [PATCH 00/11] TCP transport binding for NVMe over Fabrics Sagi Grimberg
2018-11-15 17:16 ` Sagi Grimberg
2018-11-15 17:16 ` [PATCH 01/11] ath6kl: add ath6kl_ prefix to crypto_type Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-15 17:16 ` [PATCH 02/11] iov_iter: introduce hash_and_copy iter helpers Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-15 17:16 ` [PATCH 03/11] datagram: introduce skb_copy_and_hash_datagram_iter helper Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-15 17:16 ` [PATCH 04/11] nvme-core: add work elements to struct nvme_ctrl Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-17 22:18   ` Max Gurtovoy
2018-11-17 22:18     ` Max Gurtovoy
2018-11-15 17:16 ` [PATCH 05/11] nvmet: Add install_queue callout Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-17 22:36   ` Max Gurtovoy
2018-11-17 22:36     ` Max Gurtovoy
2018-11-19 21:21     ` Sagi Grimberg [this message]
2018-11-19 21:21       ` Sagi Grimberg
2018-11-15 17:16 ` [PATCH 06/11] nvmet: allow configfs tcp trtype configuration Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-17 22:38   ` Max Gurtovoy
2018-11-17 22:38     ` Max Gurtovoy
2018-11-15 17:16 ` [PATCH 07/11] nvme-fabrics: allow user passing header digest Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-15 17:16 ` [PATCH 08/11] nvme-fabrics: allow user passing data digest Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-15 17:16 ` [PATCH 09/11] nvme-tcp: Add protocol header Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-15 17:16 ` [PATCH 10/11] nvmet-tcp: add NVMe over TCP target driver Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-17 20:15   ` David Miller
2018-11-17 20:15     ` David Miller
2018-11-17 22:48     ` Max Gurtovoy
2018-11-17 22:48       ` Max Gurtovoy
2018-11-19 21:37       ` Sagi Grimberg
2018-11-19 21:37         ` Sagi Grimberg
2018-11-19 21:26     ` Sagi Grimberg
2018-11-19 21:26       ` Sagi Grimberg
2018-11-19 22:53       ` David Miller
2018-11-19 22:53         ` David Miller
2018-11-19 23:14         ` Sagi Grimberg
2018-11-19 23:14           ` Sagi Grimberg
2018-11-19 23:18           ` David Miller
2018-11-19 23:18             ` David Miller
2018-11-19 23:24             ` Sagi Grimberg
2018-11-19 23:24               ` Sagi Grimberg
2018-11-20  1:44               ` David Miller
2018-11-20  1:44                 ` David Miller
2018-11-15 17:16 ` [PATCH 11/11] nvme-tcp: add NVMe over TCP host driver Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-15 17:16 ` [PATCH nvme-cli 12/11] nvme: Add TCP transport Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-15 17:16 ` [PATCH nvme-cli 13/11] fabrics: add tcp port tsas decoding Sagi Grimberg
2018-11-15 17:16   ` Sagi Grimberg
2018-11-15 17:16 ` [PATCH nvme-cli 14/11] fabrics: add transport header and data digest Sagi Grimberg
2018-11-15 17:16   ` 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=98230184-074a-84cf-3aa5-8ad30f2b5339@grimberg.me \
    --to=sagi@grimberg.me \
    --cc=hch@lst.de \
    --cc=keith.busch@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=maxg@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=sagi@lightbitslabs.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.