From: Leon Romanovsky <leon@kernel.org>
To: "Rita Han (she/her)" <rhan@purestorage.com>
Cc: linux-rdma@vger.kernel.org, Matthew Carlis <mattc@purestorage.com>
Subject: Re: Handling RDMA_CM_EVENT_DEVICE_REMOVAL in rdma-core
Date: Sun, 26 Jan 2025 14:53:22 +0200 [thread overview]
Message-ID: <20250126125322.GA74886@unreal> (raw)
In-Reply-To: <CAJGGzq9AhXns6y4i5LBY-g0eQY4JSV=3AG4Rt6-eMhNtE7fu4w@mail.gmail.com>
On Fri, Jan 24, 2025 at 04:30:33PM -0800, Rita Han (she/her) wrote:
> Hi all,
>
> I am currently working on validating PCIe DPC above Mellanox devices,
> and I've encountered issues where the device does not recover after
> injecting DPC above it with ENOMEM returned from rdma_create_qp. It
> seems that the rdma-core library does not support hotplugging or
> handle the removal of InfiniBand devices
> (RDMA_CM_EVENT_DEVICE_REMOVAL).
I was under impression that rdma-core supports it.
RDMA-CM disassociate support - https://github.com/linux-rdma/rdma-core/pull/750
Thanks
prev parent reply other threads:[~2025-01-26 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 0:30 Handling RDMA_CM_EVENT_DEVICE_REMOVAL in rdma-core Rita Han (she/her)
2025-01-26 12:53 ` 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=20250126125322.GA74886@unreal \
--to=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mattc@purestorage.com \
--cc=rhan@purestorage.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