From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH rdma-next] RDMA/core: Delete not-implemented get_vector_affinity
Date: Thu, 26 Feb 2026 15:44:12 +0200 [thread overview]
Message-ID: <20260226-get_vector_affinity-v1-1-910a899c4e5d@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
No drivers implement .get_vector_affinity(), and no callers invoke
ib_get_vector_affinity(), so remove it.
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
---
drivers/infiniband/core/device.c | 1 -
include/rdma/ib_verbs.h | 23 -----------------------
2 files changed, 24 deletions(-)
diff --git a/drivers/infiniband/core/device.c b/drivers/infiniband/core/device.c
index c7b227e2e657..8b1ec1f9c5e4 100644
--- a/drivers/infiniband/core/device.c
+++ b/drivers/infiniband/core/device.c
@@ -2749,7 +2749,6 @@ void ib_set_device_ops(struct ib_device *dev, const struct ib_device_ops *ops)
SET_DEVICE_OP(dev_ops, get_netdev);
SET_DEVICE_OP(dev_ops, get_numa_node);
SET_DEVICE_OP(dev_ops, get_port_immutable);
- SET_DEVICE_OP(dev_ops, get_vector_affinity);
SET_DEVICE_OP(dev_ops, get_vf_config);
SET_DEVICE_OP(dev_ops, get_vf_guid);
SET_DEVICE_OP(dev_ops, get_vf_stats);
diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h
index 1b77fd88d0fb..6e2e9019a540 100644
--- a/include/rdma/ib_verbs.h
+++ b/include/rdma/ib_verbs.h
@@ -2420,8 +2420,6 @@ struct ib_device_ops {
int (*modify_device)(struct ib_device *device, int device_modify_mask,
struct ib_device_modify *device_modify);
void (*get_dev_fw_str)(struct ib_device *device, char *str);
- const struct cpumask *(*get_vector_affinity)(struct ib_device *ibdev,
- int comp_vector);
int (*query_port)(struct ib_device *device, u32 port_num,
struct ib_port_attr *port_attr);
int (*query_port_speed)(struct ib_device *device, u32 port_num,
@@ -4826,27 +4824,6 @@ static inline __be16 ib_lid_be16(u32 lid)
return cpu_to_be16((u16)lid);
}
-/**
- * ib_get_vector_affinity - Get the affinity mappings of a given completion
- * vector
- * @device: the rdma device
- * @comp_vector: index of completion vector
- *
- * Returns NULL on failure, otherwise a corresponding cpu map of the
- * completion vector (returns all-cpus map if the device driver doesn't
- * implement get_vector_affinity).
- */
-static inline const struct cpumask *
-ib_get_vector_affinity(struct ib_device *device, int comp_vector)
-{
- if (comp_vector < 0 || comp_vector >= device->num_comp_vectors ||
- !device->ops.get_vector_affinity)
- return NULL;
-
- return device->ops.get_vector_affinity(device, comp_vector);
-
-}
-
/**
* rdma_roce_rescan_device - Rescan all of the network devices in the system
* and add their gids, as needed, to the relevant RoCE devices.
---
base-commit: 4c97e6bb1f2311be3146d5f999702392fc17f91f
change-id: 20260226-get_vector_affinity-e9fd21f4b86e
Best regards,
--
Leon Romanovsky <leonro@nvidia.com>
next reply other threads:[~2026-02-26 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 13:44 Leon Romanovsky [this message]
2026-02-27 2:57 ` [PATCH rdma-next] RDMA/core: Delete not-implemented get_vector_affinity Kalesh Anakkur Purayil
2026-03-02 19:34 ` Leon Romanovsky
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=20260226-get_vector_affinity-v1-1-910a899c4e5d@nvidia.com \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--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