From: Jason Gunthorpe <jgg@nvidia.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: sagi@grimberg.me, linux-rdma@vger.kernel.org,
sergeygo@nvidia.com, leonro@nvidia.com, oren@nvidia.com,
israelr@nvidia.com
Subject: Re: [PATCH 1/1] IB/iser: drain the entire QP during destruction flow
Date: Fri, 24 Jun 2022 16:38:26 -0300 [thread overview]
Message-ID: <20220624193826.GA240524@nvidia.com> (raw)
In-Reply-To: <20220615082839.26328-1-mgurtovoy@nvidia.com>
On Wed, Jun 15, 2022 at 11:28:39AM +0300, Max Gurtovoy wrote:
> It's important to drain both the sq and the rq to make sure all WRs were
> flushed before destroying the QP.
>
> Reviewed-by: Sergey Gorenko <sergeygo@nvidia.com>
> Reviewed-by: Israel Rukshin <israelr@nvidia.com>
> Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> ---
> drivers/infiniband/ulp/iser/iser_verbs.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2022-06-24 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 8:28 [PATCH 1/1] IB/iser: drain the entire QP during destruction flow Max Gurtovoy
2022-06-24 19:38 ` 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=20220624193826.GA240524@nvidia.com \
--to=jgg@nvidia.com \
--cc=israelr@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=oren@nvidia.com \
--cc=sagi@grimberg.me \
--cc=sergeygo@nvidia.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