From: Jason Gunthorpe <jgg@nvidia.com>
To: Max Gurtovoy <maxg@mellanox.com>
Cc: <sagi@grimberg.me>, <yaminf@mellanox.com>, <dledford@redhat.com>,
<linux-rdma@vger.kernel.org>, <leon@kernel.org>,
<bvanassche@acm.org>, <israelr@mellanox.com>, <oren@mellanox.com>,
<idanb@mellanox.com>
Subject: Re: [PATCH 1/3] IB/iser: use new shared CQ mechanism
Date: Wed, 29 Jul 2020 09:23:17 -0300 [thread overview]
Message-ID: <20200729122317.GA219420@nvidia.com> (raw)
In-Reply-To: <20200722135629.49467-1-maxg@mellanox.com>
On Wed, Jul 22, 2020 at 04:56:27PM +0300, Max Gurtovoy wrote:
> From: Yamin Friedman <yaminf@mellanox.com>
>
> Has the driver use shared CQs provided by the rdma core driver.
> Because this provides similar functionality to iser_comp it has been
> removed. Now there is no reason to allocate very large CQs when the driver
> is loaded while gaining the advantage of shared CQs.
>
> Signed-off-by: Yamin Friedman <yaminf@mellanox.com>
> Acked-by: Max Gurtovoy <maxg@mellanox.com>
> Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
> ---
> drivers/infiniband/ulp/iser/iscsi_iser.h | 23 ++-----
> drivers/infiniband/ulp/iser/iser_verbs.c | 112 +++++++------------------------
> 2 files changed, 29 insertions(+), 106 deletions(-)
No cover letter?
Applied to for-next with Bart's typo fixes
Jason
prev parent reply other threads:[~2020-07-29 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 13:56 [PATCH 1/3] IB/iser: use new shared CQ mechanism Max Gurtovoy
2020-07-22 13:56 ` [PATCH 2/3] IB/isert: " Max Gurtovoy
2020-07-29 9:39 ` Sagi Grimberg
2020-07-22 13:56 ` [PATCH 3/3] IB/srpt: " Max Gurtovoy
2020-07-22 15:02 ` Bart Van Assche
2020-07-29 9:40 ` Sagi Grimberg
2020-07-29 8:34 ` [PATCH 1/3] IB/iser: " Max Gurtovoy
2020-07-29 11:34 ` Leon Romanovsky
2020-07-29 9:39 ` Sagi Grimberg
2020-07-29 12:23 ` 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=20200729122317.GA219420@nvidia.com \
--to=jgg@nvidia.com \
--cc=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=idanb@mellanox.com \
--cc=israelr@mellanox.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maxg@mellanox.com \
--cc=oren@mellanox.com \
--cc=sagi@grimberg.me \
--cc=yaminf@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 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.