Chuck Lever
278f74b39e
RDMA/core: Move and rename trace_cm_id_create()
The restrack ID for an rdma_cm_id is not assigned until it is
associated with a device.
Here's an example I captured while testing NFS/RDMA's support for
DEVICE_REMOVAL. The new tracepoint name is "cm_id_attach".
<...>-4261 [001] 366.581299: cm_event_handler: cm.id=0 src=0.0.0.0:45919 dst=192.168.2.55:20049 tos=0 ADDR_ERROR (1/-19)
<...>-4261 [001] 366.581304: cm_event_done: cm.id=0 src=0.0.0.0:45919 dst=192.168.2.55:20049 tos=0 ADDR_ERROR consumer returns 0
<...>-1950 [000] 366.581309: cm_id_destroy: cm.id=0 src=0.0.0.0:45919 dst=192.168.2.55:20049 tos=0
<...>-7 [001] 369.589400: cm_event_handler: cm.id=0 src=0.0.0.0:49023 dst=192.168.2.55:20049 tos=0 ADDR_ERROR (1/-19)
<...>-7 [001] 369.589404: cm_event_done: cm.id=0 src=0.0.0.0:49023 dst=192.168.2.55:20049 tos=0 ADDR_ERROR consumer returns 0
<...>-1950 [000] 369.589407: cm_id_destroy: cm.id=0 src=0.0.0.0:49023 dst=192.168.2.55:20049 tos=0
<...>-4261 [001] 372.597650: cm_id_attach: cm.id=0 src=192.168.2.51:47492 dst=192.168.2.55:20049 device=mlx4_0
<...>-4261 [001] 372.597652: cm_event_handler: cm.id=0 src=192.168.2.51:47492 dst=192.168.2.55:20049 tos=0 ADDR_RESOLVED (0/0)
<...>-4261 [001] 372.597654: cm_event_done: cm.id=0 src=192.168.2.51:47492 dst=192.168.2.55:20049 tos=0 ADDR_RESOLVED consumer returns 0
<...>-4261 [001] 372.597738: cm_event_handler: cm.id=0 src=192.168.2.51:47492 dst=192.168.2.55:20049 tos=0 ROUTE_RESOLVED (2/0)
<...>-4261 [001] 372.597740: cm_event_done: cm.id=0 src=192.168.2.51:47492 dst=192.168.2.55:20049 tos=0 ROUTE_RESOLVED consumer returns 0
<...>-4691 [007] 372.600101: cm_qp_create: cm.id=0 src=192.168.2.51:47492 dst=192.168.2.55:20049 tos=0 pd.id=2 qp_type=RC send_wr=4091 recv_wr=256 qp_num=530 rc=0
<...>-4691 [007] 372.600207: cm_send_req: cm.id=0 src=192.168.2.51:47492 dst=192.168.2.55:20049 tos=0 qp_num=530
<...>-185 [002] 372.601212: cm_send_mra: cm.id=0 src=192.168.2.51:47492 dst=192.168.2.55:20049 tos=0
<...>-185 [002] 372.601362: cm_send_rtu: cm.id=0 src=192.168.2.51:47492 dst=192.168.2.55:20049 tos=0
<...>-185 [002] 372.601372: cm_event_handler: cm.id=0 src=192.168.2.51:47492 dst=192.168.2.55:20049 tos=0 ESTABLISHED (9/0)
<...>-185 [002] 372.601379: cm_event_done: cm.id=0 src=192.168.2.51:47492 dst=192.168.2.55:20049 tos=0 ESTABLISHED consumer returns 0
Fixes: ed999f820a
("RDMA/cma: Add trace points in RDMA Connection Manager")
Link: https://lore.kernel.org/r/20200530174934.21362.56754.stgit@manet.1015granger.net
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Reviewed-by: Leon Romanovsky <leonro@mellanox.com>
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
2020-06-02 20:32:54 -03:00
..
2020-05-12 21:32:52 -03:00
2018-12-19 16:28:03 -07:00
2015-06-12 14:49:18 -04:00
2020-05-12 11:47:48 -03:00
2019-06-05 17:36:37 +02:00
2020-01-25 15:11:37 -04:00
2020-05-27 16:05:05 -03:00
2020-05-22 15:37:19 -03:00
2020-05-27 16:05:05 -03:00
2020-01-07 16:10:53 -04:00
2020-06-02 20:32:54 -03:00
2020-06-02 20:32:54 -03:00
2020-05-29 16:09:02 -03:00
2019-12-12 15:38:15 -05:00
2020-05-29 16:09:02 -03:00
2020-06-02 20:32:54 -03:00
2020-01-25 14:48:33 -04:00
2020-03-04 14:28:25 -04:00
2016-08-02 13:15:18 -04:00
2019-08-27 13:09:23 -03:00
2019-08-27 13:09:23 -03:00
2019-10-22 14:45:31 -03:00
2020-05-06 16:51:43 -03:00
2020-02-20 13:33:51 -04:00
2018-12-19 16:28:03 -07:00
2020-05-06 11:57:33 -03:00
2020-06-02 20:32:53 -03:00
2019-06-28 21:18:23 -03:00
2020-05-06 11:57:33 -03:00
2019-10-24 20:49:37 -03:00
2020-05-12 11:47:48 -03:00
2018-12-12 07:40:16 -07:00
2016-03-03 10:20:25 -05:00
2020-05-21 20:10:46 -03:00
2020-05-21 20:39:36 -03:00
2019-10-23 15:58:31 -03:00
2019-10-23 15:58:31 -03:00
2019-06-02 18:06:26 -07:00
2020-04-15 11:34:49 -03:00
2020-05-27 13:46:05 -03:00
2018-10-16 13:34:01 -04:00
2020-03-24 19:53:25 -03:00
2015-07-14 13:20:08 -04:00
2018-12-12 07:40:16 -07:00
2020-05-29 15:35:49 -03:00
2020-01-07 16:10:53 -04:00
2020-05-27 16:05:05 -03:00
2020-05-27 13:46:05 -03:00
2020-03-10 14:29:07 -03:00
2020-02-13 13:38:02 -04:00
2020-05-06 11:57:33 -03:00
2020-06-02 20:32:54 -03:00
2020-05-27 13:46:05 -03:00
2020-05-21 20:34:53 -03:00
2018-06-25 14:19:57 -06:00
2020-05-12 17:02:25 -03:00
2019-04-08 13:05:25 -03:00
2020-05-21 20:34:53 -03:00
2020-01-16 15:55:46 -04:00
2019-04-08 13:05:25 -03:00
2019-04-08 13:05:25 -03:00
2020-05-21 20:10:46 -03:00
2020-05-21 20:39:36 -03:00
2020-05-21 20:39:35 -03:00
2020-05-21 20:39:35 -03:00
2020-05-21 20:39:36 -03:00
2020-05-21 20:39:36 -03:00
2020-05-21 20:34:53 -03:00
2020-06-02 20:32:54 -03:00