public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Dennis Dalessandro
	<dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: RDMA mailing list <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: OmniPath physical state bits
Date: Tue, 1 Aug 2017 21:43:08 +0300	[thread overview]
Message-ID: <20170801184308.GR13672@mtr-leonro.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]

Hi Dennis,

I'm almost finished to work on the third wave of my RDMAtool patches -
expose through UAPI various device capability bits, physical states, e.t.c.

While writing rdma_link_phys_state bits, I saw that OmniPath using 8-15
bits and I would like to add ability for RDMAtool to handle it properly.

The last piece before I can send the patches is the lack of
documentation for those bits. Can you please provide short description
for them so I'll be able to add it to the exported header file?
It will serve as a documentation for the RDAMtool users.

Right now, it looks like this:

156 /*
157  * When writing this field, only values 0, 1, 2, and 3
158  * are valid. Other values are ignored. See InfiniBand Architecture
159  * Specification Volume 2, Link/Phy Interface chapter.
160  */
161 enum rdma_link_phys_state {
162         /*
163          * 0 - 7 are according to the IB specification
164          * 8 - 15 -  Reserved and ignored in IB, but partially
165          *           in use by OmniPath
166          */
167         RDMA_LINK_PHYS_STATE_NOP,
168         RDMA_LINK_PHYS_STATE_SLEEP,
169         RDMA_LINK_PHYS_STATE_POLLING,
170         RDMA_LINK_PHYS_STATE_DISABLED,
171         RDMA_LINK_PHYS_STATE_PORT_CONFIGURATION_TRAINING,
172         RDMA_LINK_PHYS_STATE_LINK_UP,
173         RDMA_LINK_PHYS_STATE_LINK_ERROR_RECOVER,
174         RDMA_LINK_PHYS_STATE_LINK_PHY_TEST,
175         /* 8 is reserved */
176         RDMA_LINK_PHYS_STATE_OFFLINE = 9,
177         RDMA_LINK_PHYS_STATE_GANGED,
178         RDMA_LINK_PHYS_STATE_TEST,
179         RDMA_LINK_PHYS_STATE_MAX,
180         /* values 12-15 are reserved/ignored */
181 };

Thanks

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2017-08-01 18:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170801184308.GR13672@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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