From: Christoph Hellwig <hch@lst.de>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, hch@lst.de, kbusch@kernel.org,
chaitanyak@nvidia.com, israelr@nvidia.com,
mruijter@primelogic.nl, oren@nvidia.com, nitzanc@nvidia.com
Subject: Re: [PATCH 2/2] nvmet-rdma: implement get_queue_size controller op
Date: Wed, 22 Sep 2021 09:45:50 +0200 [thread overview]
Message-ID: <20210922074550.GA16099@lst.de> (raw)
In-Reply-To: <300d5661-c22c-bb8f-e5c3-38902dd946a0@nvidia.com>
On Wed, Sep 22, 2021 at 10:44:20AM +0300, Max Gurtovoy wrote:
> So for now, as mentioned, till we have some ib_ API, lets set it to 128.
Please just add the proper ib_ API, it should not be a whole lot of
work as we already do that calculation anyway for the R/W API setup.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-09-22 7:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 19:04 [PATCH v1 0/2] update RDMA controllers queue depth Max Gurtovoy
2021-09-21 19:04 ` [PATCH 1/2] nvmet: add get_queue_size op for controllers Max Gurtovoy
2021-09-21 19:20 ` Chaitanya Kulkarni
2021-09-21 22:47 ` Sagi Grimberg
2021-09-22 7:35 ` Max Gurtovoy
2021-09-21 19:04 ` [PATCH 2/2] nvmet-rdma: implement get_queue_size controller op Max Gurtovoy
2021-09-21 19:21 ` Chaitanya Kulkarni
2021-09-21 22:52 ` Sagi Grimberg
2021-09-22 7:44 ` Max Gurtovoy
2021-09-22 7:45 ` Christoph Hellwig [this message]
2021-09-22 8:10 ` Max Gurtovoy
2021-09-22 9:18 ` Sagi Grimberg
2021-09-22 9:35 ` Max Gurtovoy
2021-09-22 12:10 ` Jason Gunthorpe
2021-09-22 12:57 ` Max Gurtovoy
2021-09-22 13:31 ` Jason Gunthorpe
2021-09-22 14:00 ` Max Gurtovoy
2021-09-21 19:22 ` [PATCH v1 0/2] update RDMA controllers queue depth Chaitanya Kulkarni
2021-09-21 19:42 ` Mark Ruijter
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=20210922074550.GA16099@lst.de \
--to=hch@lst.de \
--cc=chaitanyak@nvidia.com \
--cc=israelr@nvidia.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mgurtovoy@nvidia.com \
--cc=mruijter@primelogic.nl \
--cc=nitzanc@nvidia.com \
--cc=oren@nvidia.com \
--cc=sagi@grimberg.me \
/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