RE: dumping queue state

Steve Wise
2017-12-20T17:42:22Z

> WIP: no manuals, no review yet and not massively tested - but works for me
:
>
>
> >
> > Is there a way to extend commands with provider-specific data?
> >
>
> In future yes, rdmatool provides "-d" option (detailed output) and IMHO
> all vendor specific will got there.

Cool.

Looksie:

[root@stevo1 iproute2]# ./rdma/rdma res
1: mlx4_0: curr/max: pd 4/32764 cq 17/65408 qp 3/163768
2: cxgb4_0: curr/max: pd 2/65536 cq 16/24576 qp 2/12288
2: cxgb4_0: curr/max: pd 2/65536 cq 16/24576 qp 2/12288

[root@stevo1 iproute2]# ./rdma/rdma res show qp link cxgb4_0
DEV/PORT LQPN TYPE STATE PID COMM
cxgb4_0/- 1028 RC RTS 0 [rdma-cm]
cxgb4_0/- 1026 RC RTS 0 [rdma-cm]

I'm not sure why the port is not specified on the above cxgb4 QPs which are
connected. They should have a port number. But perhaps it isn't filled in
correctly in the cm_id or something?

[root@stevo1 iproute2]# ./rdma/rdma res show qp link mlx4_0
DEV/PORT LQPN TYPE STATE PID COMM
mlx4_0/1 537 RC RTS 0 [rdma-cm]
mlx4_0/1 536 RC RTS 0 [rdma-cm]
mlx4_0/1 1 GSI RTS 0 [rdma-mad]
[root@stevo1 iproute2]#

rdma should probably understand enough transport-specific details to not
display ib-specific stuff on an iwarp qp. Here PSNs and PATH-MIG are all
IB-specific:

[root@stevo1 iproute2]# ./rdma/rdma res show qp link cxgb4_0 -d
DEV/PORT LQPN RQPN TYPE STATE PID COMM
SQ-PSN RQ-PSN PATH-MIG
cxgb4_0/- 1028 0 RC RTS 0 [rdma-cm] 0
0 MIGRATED
cxgb4_0/- 1026 0 RC RTS 0 [rdma-cm] 0
0 MIGRATED

[root@stevo1 iproute2]# ./rdma/rdma res show qp link mlx4_0 -d
DEV/PORT LQPN RQPN TYPE STATE PID COMM
SQ-PSN RQ-PSN PATH-MIG
mlx4_0/1 537 537 RC RTS 0 [rdma-cm]
13145128 12441844 MIGRATED
mlx4_0/1 536 536 RC RTS 0 [rdma-cm]
14218681 1982803 MIGRATED
mlx4_0/1 1 --- GSI RTS 0 [rdma-mad] 0
--- ---

Looking good though!

Why did you prefer netlink vs debugfs for this stuff? (I'm sure it was
discussed on the list but I missed it).

Steve.