Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 2/3] nvmet-rdma: use SRQ per completion vector
Date: Thu, 7 Sep 2017 14:03:21 +0200	[thread overview]
Message-ID: <20170907120321.GC18794@lst.de> (raw)
In-Reply-To: <4efc8d9b-a9d6-0297-9aff-e078bfdaa7f6@grimberg.me>

On Wed, Sep 06, 2017@05:57:47PM +0300, Sagi Grimberg wrote:
>
>>>     	int			idx;
>>>   	int			host_qid;
>>> +	int			comp_vector;
>>
>> How will this interact with these changes:
>>
>> http://git.infradead.org/users/hch/rdma.git/shortlog/refs/heads/rdma-cq.2
>>
>> which I'd really like to see in?
>
> I have another spin on that one (plus the fine-grained affinity
> assignments addition that I proposed to nvmet a while ago).
>
> You can see it here:
> git://git.infradead.org/users/sagi/linux.git rdma-cq-pool

Tiem to get it out to the list :)  Chuck was also really interested
in some of this for NFS.

  reply	other threads:[~2017-09-07 12:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 10:59 [PATCH 0/3] nvmet-rdma: SRQ per completion vector Max Gurtovoy
2017-09-05 10:59 ` [PATCH 1/3] nvmet-rdma: use srq pointer in rdma_cmd Max Gurtovoy
2017-09-06 10:30   ` Christoph Hellwig
2017-09-05 10:59 ` [PATCH 2/3] nvmet-rdma: use SRQ per completion vector Max Gurtovoy
2017-09-06 10:38   ` Christoph Hellwig
2017-09-06 14:57     ` Sagi Grimberg
2017-09-07 12:03       ` Christoph Hellwig [this message]
2017-09-06 14:50   ` Sagi Grimberg
2017-09-07 10:47     ` Max Gurtovoy
2017-09-05 10:59 ` [PATCH 3/3] nvmet-rdma: add module parameter for SRQ size Max Gurtovoy
2017-09-06 10:39   ` Christoph Hellwig
2017-09-06 15:02   ` Sagi Grimberg
2017-09-06 14:40 ` [PATCH 0/3] nvmet-rdma: SRQ per completion vector Sagi Grimberg
2017-11-07 14:40 ` Max Gurtovoy
2017-11-08 10:07   ` 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=20170907120321.GC18794@lst.de \
    --to=hch@lst.de \
    /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