From: Hal Rosenstock <hal@dev.mellanox.co.il>
To: Aishwarya Pant <aishpant@gmail.com>
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 08:16:55 -0500 [thread overview]
Message-ID: <6aca6ebc-4e58-79c7-6767-9e370c8ef71d@dev.mellanox.co.il> (raw)
In-Reply-To: <20180205071934.GA9185@mordor.localdomain>
On 2/5/2018 2:19 AM, Aishwarya Pant wrote:
>>> + 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?
In terms of IB, PortInfo:CapabilityMask is RO from perspective of SM.
In linux, IsSM is settable via open of issmN file. An SM will do this to
set the IsSM bit.
It is similar in terms of IsCommunicationManagementSupported bit where
bit is set when CM module is loaded in kernel (in cm_add_one).
-- Hal
> Aishwarya
>
> <snip>
>
next prev parent reply other threads:[~2018-02-05 13:16 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
2018-02-05 13:16 ` Hal Rosenstock [this message]
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=6aca6ebc-4e58-79c7-6767-9e370c8ef71d@dev.mellanox.co.il \
--to=hal@dev.mellanox.co.il \
--cc=aishpant@gmail.com \
--cc=corbet@lwn.net \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--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®