IB/umad: Enable support only for IB ports
PATCH v8 3/11 IB/umad: Enable support only for IB ports
Initialize umad context only for Infiniband (as opposed to Ethernet) ports.
--- drivers/infiniband/core/user_mad.c | 11 +++++++---- 1 files changed, 7 insertions(+), 4 deletions(-)
drivers/infiniband/core/user_mad.c +7 -4
@@ -1138,8 +1138,9 @@ static void ib_umad_add_one(struct ib_device *device)for (i = s; i <= e; ++i) { umad_dev->port[i - s].umad_dev = umad_dev; -if (ib_umad_init_port (device, i, &umad_dev->port[i - s])) - goto err; +if (rdma_port_link_layer (device, i) ==IB_LINK_LAYER_INFINIBAND ) +if (ib_umad_init_port (device, i, &umad_dev->port[i - s])) + goto err; }ib_set_client_data (device, &umad_client, umad_dev);
@@ -1148,7 +1149,8 @@ static void ib_umad_add_one(struct ib_device *device) err:while (--i >= s) -ib_umad_kill_port (&umad_dev->port[i - s]); +if (rdma_port_link_layer (device, i) ==IB_LINK_LAYER_INFINIBAND ) +ib_umad_kill_port (&umad_dev->port[i - s]);kref_put (&umad_dev->ref, ib_umad_release_dev); }
@@ -1162,7 +1164,8 @@ static void ib_umad_remove_one(struct ib_device *device)return ;for (i =0 ; i <= umad_dev->end_port - umad_dev->start_port; ++i) -ib_umad_kill_port (&umad_dev->port[i]); +if (rdma_port_link_layer (device, i +1 ) ==IB_LINK_LAYER_INFINIBAND ) +ib_umad_kill_port (&umad_dev->port[i]);kref_put (&umad_dev->ref, ib_umad_release_dev); }
Signature · 6 lines
1.7.0 -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Why do we not allow umad for IBoE ports? I understand there's no QP0 but why can't userspace use QP1 just like for IB link layer ports?
Signature · 6 lines
Roland Dreier <[email protected]> || For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): adazl0eatj6.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org
Quoted 2 lines · Roland Dreier
Why do we not allow umad for IBoE ports? I understand there's no QP0 but why can't userspace use QP1 just like for IB link layer ports?
Currently QP1 is only used by the CM protocol which is implemented in the kernel.
Since we handle the iboe specific flow in the cma rather than the SA, there is no need to expose qp1 to userspace.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 20100506104848.GA29792-8YAHvHwT2UEvbXDkjdHOrw/[email protected]
Quoted 5 lines · Eli Cohen
Quoted 2 lines · Roland Dreier
Why do we not allow umad for IBoE ports? I understand there's no QP0 but why can't userspace use QP1 just like for IB link layer ports?
Currently QP1 is only used by the CM protocol which is implemented in the kernel. Since we handle the iboe specific flow in the cma rather than the SA, there is no need to expose qp1 to userspace.
Eli, any reason not to let reading (e.g perfquery) the HCA/port traffic counters with IBoE?
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 4BEF80D9.5060200-smomgflXvOZWk0Htik3J/[email protected]
Quoted 3 lines · Or Gerlitz
Eli, any reason not to let reading (e.g perfquery) the HCA/port traffic counters with IBoE?
RoCE assumes Eth management practices (including performance management). But this is an interesting idea that we can consider for the future.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html