mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aishwarya Pant <aishpant@gmail.com>
To: Hal Rosenstock <hal@dev.mellanox.co.il>
Cc: Doug Ledford <dledford@redhat.com>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jonathan Corbet <corbet@lwn.net>,
	Greg KH <gregkh@linuxfoundation.org>,
	linux-doc@vger.kernel.org, Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: [PATCH] Documentation/ABI: update infiniband sysfs interfaces
Date: Mon, 5 Feb 2018 12:49:34 +0530	[thread overview]
Message-ID: <20180205071934.GA9185@mordor.localdomain> (raw)
In-Reply-To: <64f953cc-7831-1164-28b5-5319e72e600f@dev.mellanox.co.il>

On Thu, Feb 01, 2018 at 12:48:18PM -0500, Hal Rosenstock wrote:
> On 2/1/2018 8:32 AM, Aishwarya Pant wrote:
> > Add documentation for core and hardware specific infiniband interfaces.
> > The descriptions have been collected from git commit logs, reading
> > through code and data sheets. Some drivers have incomplete doc and are
> > annotated with the comment '[to be documented]'.
> > 
> > Signed-off-by: Aishwarya Pant <aishpant@gmail.com>
> > ---
> >  Documentation/ABI/testing/sysfs-class-infiniband | 755 +++++++++++++++++++++++
> >  1 file changed, 755 insertions(+)
> > 
> > diff --git a/Documentation/ABI/testing/sysfs-class-infiniband b/Documentation/ABI/testing/sysfs-class-infiniband
> > index a86abe66a316..2e150169633b 100644
> > --- a/Documentation/ABI/testing/sysfs-class-infiniband
> > +++ b/Documentation/ABI/testing/sysfs-class-infiniband
> > @@ -1,3 +1,194 @@
> > +sysfs interface common for all infiniband devices
> > +-------------------------------------------------
> > +
> > +What:		/sys/class/infiniband/<device>/node_type
> > +What:		/sys/class/infiniband/<device>/node_guid
> > +What:		/sys/class/infiniband/<device>/sys_image_guid
> > +Date:		Apr, 2005
> > +KernelVersion:	v2.6.12
> > +Contact:	linux-rdma@vger.kernel.org
> > +Description:
> > +		node_type:	(RO) Node type (CA, RNIC, usNIC, usNIC UDP,
> > +				switch or router)
> > +
> > +		node_guid:	(RO) Node GUID
> > +
> > +		sys_image_guid:	(RO) System image GUID
> > +
> > +
> > +What:		/sys/class/infiniband/<device>/node_desc
> > +Date:		Feb, 2006
> > +KernelVersion:	v2.6.17
> > +Contact:	linux-rdma@vger.kernel.org
> > +Description:
> > +		(RW) Update the node description with information such as the
> > +		node's hostname, so that IB network management software can tie
> > +		its view to the real world.
> > +
> > +
> > +What:		/sys/class/infiniband/<device>/fw_ver
> > +Date:		Jun, 2016
> > +KernelVersion:	v4.10
> > +Contact:	linux-rdma@vger.kernel.org
> > +Description:
> > +		(RO) Display firmware version
> > +
> > +
> > +What:		/sys/class/infiniband/<device>/ports/<port-num>/lid
> > +What:		/sys/class/infiniband/<device>/ports/<port-num>/rate
> > +What:		/sys/class/infiniband/<device>/ports/<port-num>/lid_mask_count
> > +What:		/sys/class/infiniband/<device>/ports/<port-num>/sm_sl
> > +What:		/sys/class/infiniband/<device>/ports/<port-num>/sm_lid
> > +What:		/sys/class/infiniband/<device>/ports/<port-num>/state
> > +What:		/sys/class/infiniband/<device>/ports/<port-num>/phys_state
> > +What:		/sys/class/infiniband/<device>/ports/<port-num>/cap_mask
> > +Date:		Apr, 2005
> > +KernelVersion:	v2.6.12
> > +Contact:	linux-rdma@vger.kernel.org
> > +Description:
> > +
> > +		lid:		(RO) Port LID
> > +
> > +		rate:		(RO) Port data rate (active width * active
> > +				speed)
> > +
> > +		lid_mask_count:	(RO) Port LID mask count
> > +
> > +		sm_slL		(RO) Subnet manager SL for port's subnet
> 
> Typo sm_sl:
> 
> > +
> > +		sm_lid:		(RO) Subnet manager LID for port's subnet
> > +
> > +		state:		(RO) Port state (DOWN, INIT, ARMED, ACTIVE or
> > +				ACTIVE_DEFER> +
> > +		phys_state:	(RO) Port physical state (Sleep, Polling,
> > +				LinkUp, etc)
> > +
> > +		cap_mask:	(RO) Port capability mask
> 
> 2 bits here are settable: IsCommunicationManagementSupported and IsSM.

Hi

Sorry, I don't quite understand this. cap_mask is a read only value which
indicates the supported functions. So the two bits-
IsCommunicationManagementSupported and IsSM, should not be setttable?

Aishwarya

<snip>

  reply	other threads:[~2018-02-05  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 13:32 Aishwarya Pant
2018-02-01 17:48 ` Hal Rosenstock
2018-02-05  7:19   ` Aishwarya Pant [this message]
2018-02-05 13:16     ` Hal Rosenstock
2018-02-01 22:08 ` Jason Gunthorpe
2018-02-02  8:26   ` Aishwarya Pant

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=20180205071934.GA9185@mordor.localdomain \
    --to=aishpant@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dledford@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hal@dev.mellanox.co.il \
    --cc=jgg@ziepe.ca \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®