[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170626182924.GB16026@obsidianresearch.com>
Date: Mon, 26 Jun 2017 12:29:24 -0600
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: Leon Romanovsky <leon@...nel.org>
Cc: Stephen Hemminger <stephen@...workplumber.org>,
Leon Romanovsky <leonro@...lanox.com>,
Doug Ledford <dledford@...hat.com>,
Ariel Almog <ariela@...lanox.com>,
Dennis Dalessandro <dennis.dalessandro@...el.com>,
Linux RDMA <linux-rdma@...r.kernel.org>,
Linux Netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH iproute2 3/5] rdma: Add device capability parsing
On Mon, Jun 26, 2017 at 09:21:26PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...lanox.com>
>
> Add parsing interface for the device capability flags
>
> $ rdma dev show
> 1: mlx5_0: caps 0x1257e1c26
This seems very un ip-like. I wouldn't show an undecoded hex value
like that, it isn't really useful.
> $ rdma dev show mlx5_4 caps
> 5: mlx5_4: caps 0x1257e1c26
> Bit Description
> 01 DEVICE_BAD_PKEY_CNTR
> 02 DEVICE_BAD_QKEY_CNTR
This table also seems un ip-like, the usual format is a list of words,
I think.
> $ rdma dev show mlx5_4 cap_flags
> Unknown parameter 'caps_flags'.
?
Jason
Powered by blists - more mailing lists