Skip to content

Allow ib_clients to nullify .add but still get .remove events reliably

Doug Ledford linux-nvme linux-rdma 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v2 Latest0 of 3 patches 0 repliesNew

Patches in v2 No applies recorded yet

None of the 3 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [PATCH v2 0/3] Allow ib_clients to nullify .add but still get .remove events reliably
Quoted 21 lines · Max Gurtovoy
Quoted 19 lines · Sagi Grimberg

Some ULPs are just interested in device removal notification with no specific
association because they work over RDMA_CM so no need for detecting appearance
of the devices. That wasn't the because the corresponding ib_client_data
was never added to the device clients list when the ib_client registers,
Patch 1 fixes it. Patches 2-3 just removes the empty .add callout nvme(t)-rdma set.

Changes from v1:
- reword patch 1 change log title
- collected review tags

Note that this will create a conflict with jens's for-4.13 which we added
ib_client registration to nvmet-rdma.

Quoted 8 lines
Quoted 4 lines

Sagi Grimberg (3):
RDMA/core: make ib_device.add method optional
nvme-rdma: remove redundant empty device add callout
nvmet-rdma: remove redundant empty device add callout

All these patches looks fine to me,

Reviewed-by Max Gurtovoy <maxg at mellanox.com>

Thanks, series applied.

Signature · 3 lines
Doug Ledford <dledford at redhat.com>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

Read the cover letter in its thread