Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: Chiara Meiohas <cmeiohas@nvidia.com>, linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-next 1/2] RDMA/core: Add an option to display driver-specific QPs in the rdmatool
Date: Tue, 30 Apr 2024 13:18:55 +0300	[thread overview]
Message-ID: <171447233535.87755.5228812010570551466.b4-ty@kernel.org> (raw)
In-Reply-To: <2607bb3ddec3cae3443c2ea19e9f700825d20a98.1713268997.git.leon@kernel.org>


On Tue, 16 Apr 2024 15:03:50 +0300, Leon Romanovsky wrote:
> Utilize the -dd flag (driver-specific details) in the rdmatool
> to view driver-specific QPs which are not exposed yet.
> 
> Add the netlink attribute to mark request to convey driver details and
> use it to return QP subtype as a string.
> 
> $ rdma resource show qp link ibp8s0f1
> link ibp8s0f1/1 lqpn 360 type UD state RTS sq-psn 0 comm [mlx5_ib]
> link ibp8s0f1/1 lqpn 0 type SMI state RTS sq-psn 0 comm [ib_core]
> link ibp8s0f1/1 lqpn 1 type GSI state RTS sq-psn 0 comm [ib_core]
> 
> [...]

Applied, thanks!

[1/2] RDMA/core: Add an option to display driver-specific QPs in the rdmatool
      https://git.kernel.org/rdma/rdma/c/e18fa0bbcedf82
[2/2] RDMA/mlx5: Track DCT, DCI and REG_UMR QPs as diver_detail resources.
      https://git.kernel.org/rdma/rdma/c/fd3af5e21866b7

Best regards,
-- 
Leon Romanovsky <leon@kernel.org>


      parent reply	other threads:[~2024-04-30 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 12:03 [PATCH rdma-next 1/2] RDMA/core: Add an option to display driver-specific QPs in the rdmatool Leon Romanovsky
2024-04-16 12:03 ` [PATCH rdma-next 2/2] RDMA/mlx5: Track DCT, DCI and REG_UMR QPs as diver_detail resources Leon Romanovsky
2024-04-30 10:18 ` Leon Romanovsky [this message]

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=171447233535.87755.5228812010570551466.b4-ty@kernel.org \
    --to=leon@kernel.org \
    --cc=cmeiohas@nvidia.com \
    --cc=jgg@ziepe.ca \
    --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