From: Jason Gunthorpe <jgg@nvidia.com>
To: Max Gurtovoy <maxg@mellanox.com>
Cc: <sagi@grimberg.me>, <krishna2@chelsio.com>,
<linux-rdma@vger.kernel.org>, <leonro@mellanox.com>,
<israelr@mellanox.com>, <nirranjan@chelsio.com>,
<bharat@chelsio.com>, <oren@mellanox.com>
Subject: Re: [PATCH 1/1] IB/isert: allocate RW ctxs according to max IO size
Date: Thu, 16 Jul 2020 14:31:13 -0300 [thread overview]
Message-ID: <20200716173113.GA2647180@nvidia.com> (raw)
In-Reply-To: <20200708091908.162263-1-maxg@mellanox.com>
On Wed, Jul 08, 2020 at 12:19:08PM +0300, Max Gurtovoy wrote:
> Current iSER target code allocates MR pool budget based on queue size.
> Since there is no handshake between iSER initiator and target on max IO
> size, we'll set the iSER target to support upto 16MiB IO operations and
> allocate the correct number of RDMA ctxs according to the factor of MR's
> per IO operation. This would guaranty sufficient size of the MR pool for
> the required IO queue depth and IO size.
>
> Reported-by: Krishnamraju Eraparaju <krishna2@chelsio.com>
> Tested-by: Krishnamraju Eraparaju <krishna2@chelsio.com>
> Signed-off-by: Max Gurtovoy <maxg@mellanox.com>
> Acked-by: Sagi Grimberg <sagi@grimberg.me>
> ---
> drivers/infiniband/ulp/isert/ib_isert.c | 6 ++++--
> drivers/infiniband/ulp/isert/ib_isert.h | 3 ++-
> 2 files changed, 6 insertions(+), 3 deletions(-)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2020-07-16 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 9:19 [PATCH 1/1] IB/isert: allocate RW ctxs according to max IO size Max Gurtovoy
2020-07-10 4:54 ` Sagi Grimberg
2020-07-16 17:31 ` Jason Gunthorpe [this message]
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=20200716173113.GA2647180@nvidia.com \
--to=jgg@nvidia.com \
--cc=bharat@chelsio.com \
--cc=israelr@mellanox.com \
--cc=krishna2@chelsio.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maxg@mellanox.com \
--cc=nirranjan@chelsio.com \
--cc=oren@mellanox.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 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.