From: Leon Romanovsky <leonro@nvidia.com>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: <jgg@nvidia.com>, Dean Luick <dean.luick@cornelisnetworks.com>,
<linux-rdma@vger.kernel.org>
Subject: Re: [PATCH for-rc 0/6] HFI fixups around expected recv
Date: Tue, 10 Jan 2023 12:17:38 +0200 [thread overview]
Message-ID: <Y707Qv31FXlAz2SF@unreal> (raw)
In-Reply-To: <167328512911.1472310.3529280633243532911.stgit@awfm-02.cornelisnetworks.com>
On Mon, Jan 09, 2023 at 12:31:00PM -0500, Dennis Dalessandro wrote:
> While working on a FIXME for next cycle Dean found some other issues that we
> should probably try to get in for RC. Mostly in the error/teardown case but this
> also has a change to reserve expected TIDs which is the more correc behavior and
> enables the follow on patches for the FIXME.
>
> ---
>
> Dean Luick (6):
> IB/hfi1: Restore allocated resources on failed copyout
This needs to be resent.
> IB/hfi1: Reject a zero-length user expected buffer
> IB/hfi1: Reserve user expected TIDs
> IB/hfi1: Fix expected receive setup error exit issues
> IB/hfi1: Immediately remove invalid memory from hardware
> IB/hfi1: Remove user expected buffer invalidate race
These applied to -rc.
Thanks
>
>
> drivers/infiniband/hw/hfi1/file_ops.c | 5 +-
> drivers/infiniband/hw/hfi1/user_exp_rcv.c | 200 +++++++++++++++-------
> drivers/infiniband/hw/hfi1/user_exp_rcv.h | 3 +
> 3 files changed, 147 insertions(+), 61 deletions(-)
>
> --
> -Denny
>
prev parent reply other threads:[~2023-01-10 10:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 17:31 [PATCH for-rc 0/6] HFI fixups around expected recv Dennis Dalessandro
2023-01-09 17:31 ` [PATCH for-rc 1/6] IB/hfi1: Restore allocated resources on failed copyout Dennis Dalessandro
2023-01-10 10:12 ` Leon Romanovsky
2023-01-09 17:31 ` [PATCH for-rc 2/6] IB/hfi1: Reject a zero-length user expected buffer Dennis Dalessandro
2023-01-09 17:31 ` [PATCH for-rc 3/6] IB/hfi1: Reserve user expected TIDs Dennis Dalessandro
2023-01-09 17:31 ` [PATCH for-rc 4/6] IB/hfi1: Fix expected receive setup error exit issues Dennis Dalessandro
2023-01-09 17:31 ` [PATCH for-rc 5/6] IB/hfi1: Immediately remove invalid memory from hardware Dennis Dalessandro
2023-01-09 17:31 ` [PATCH for-rc 6/6] IB/hfi1: Remove user expected buffer invalidate race Dennis Dalessandro
2023-01-16 15:41 ` Jason Gunthorpe
2023-01-17 19:19 ` Dean Luick
2023-01-18 12:42 ` Jason Gunthorpe
2023-01-19 16:00 ` Dean Luick
2023-01-19 18:05 ` Jason Gunthorpe
2023-01-20 16:09 ` Dean Luick
2023-01-10 10:17 ` Leon Romanovsky [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=Y707Qv31FXlAz2SF@unreal \
--to=leonro@nvidia.com \
--cc=dean.luick@cornelisnetworks.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).