From: maxg@mellanox.com (Max Gurtovoy)
Subject: [PATCH v2 0/3] nvmet-rdma: SRQ per completion vector
Date: Sat, 18 Nov 2017 15:57:15 +0200 [thread overview]
Message-ID: <935af437-d69e-e258-c00a-8bf9a04f9988@mellanox.com> (raw)
In-Reply-To: <20171118125229.GT18825@mtr-leonro.local>
On 11/18/2017 2:52 PM, Leon Romanovsky wrote:
> On Fri, Nov 17, 2017@09:32:42PM +0200, Max Gurtovoy wrote:
>>
>>
>> On 11/16/2017 8:36 PM, Sagi Grimberg wrote:
>>>
>>>> Since there is an active discussion regarding the CQ pool
>>>> architecture, I decided to push
>>>> this feature (maybe it can be pushed before CQ pool).
>>>>
>>>> This is a new feature for NVMEoF RDMA target,
>>>
>>> Any chance having this for the rest? isert, srpt, svcrdma?
>>>
>>
>> We can implement it for isert, but I think it's better to see how the CQ
>> pool will be defined first.
>> It can bring a big benefit and improvement for ib_srpt (similar to NVMEoF
>> target) but I'm not sure if I can commit for that one soon..
>
> Too bad, but I don't see inclusion of generic SRQ pool code in RDMA
> subsystem without actual conversion of existing ULP clients.
>
> Thanks
>
This patchset adds this feature to NVMEoF target so actually there are
ULPs that use it. Same issue we have with mr_pool that only RDMA rw.c
use it (Now we're adding it to NVMEoF initiators too - in review).
I can add srq_pool to iSER target code but I don't want to re-write it
again in few weeks, when the CQ pool will be added.
Regarding other ULPs, we don't have a testing environment for them so I
prefer not to commit on their implementation in the near future.
I don't know why we can't add this feature "as is".
Other ULPs maintainers might use it once it will be pushed.
next prev parent reply other threads:[~2017-11-18 13:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 17:21 [PATCH v2 0/3] nvmet-rdma: SRQ per completion vector Max Gurtovoy
2017-11-16 17:21 ` [PATCH 1/3] IB/core: add a simple SRQ pool per PD Max Gurtovoy
2017-11-16 18:10 ` Leon Romanovsky
2017-11-17 19:12 ` Max Gurtovoy
2017-11-18 7:36 ` Leon Romanovsky
2017-11-16 18:32 ` Sagi Grimberg
2017-11-17 19:17 ` Max Gurtovoy
2017-11-16 17:21 ` [PATCH 2/3] nvmet-rdma: use srq pointer in rdma_cmd Max Gurtovoy
2017-11-16 17:26 ` [Suspected-Phishing][PATCH " Max Gurtovoy
2017-11-16 18:37 ` [PATCH " Sagi Grimberg
2017-11-16 17:21 ` [PATCH 3/3] nvmet-rdma: use SRQ per completion vector Max Gurtovoy
2017-11-16 18:08 ` [PATCH v2 0/3] nvmet-rdma: " Leon Romanovsky
2017-11-17 19:18 ` Max Gurtovoy
2017-11-16 18:36 ` Sagi Grimberg
2017-11-17 19:32 ` Max Gurtovoy
2017-11-18 12:52 ` Leon Romanovsky
2017-11-18 13:57 ` Max Gurtovoy [this message]
2017-11-18 14:40 ` Leon Romanovsky
2017-11-18 21:29 ` Max Gurtovoy
2017-11-20 11:00 ` Sagi Grimberg
2017-11-20 11:34 ` Leon Romanovsky
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=935af437-d69e-e258-c00a-8bf9a04f9988@mellanox.com \
--to=maxg@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox