public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Vangelis Tasoulas <vangelis-S8y2klWGCOFhl2p70BpVqQ@public.gmane.org>
To: "Weiny, Ira" <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Linux RDMA Mailing List
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Are the PathRecord reserved components really reserved?
Date: Mon, 25 Aug 2014 22:27:28 +0200	[thread overview]
Message-ID: <53FB9C30.2000904@simula.no> (raw)
In-Reply-To: <2807E5FD2F6FDA4886F6618EAC48510E0CAD282C-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>

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

Thanks Ira,

I found the corresponding document.

Vangelis

On 08/25/2014 04:49 PM, Weiny, Ira wrote:
>>
>> Hello,
>>
>> I am looking into the OFED code for the component mask bits of the
>> PathRecord requests and I need some further explanation.
>>
>> The IB specification in section "15.2.5.16 PathRecord, table 207 PathRecord"
>> defines the first two components as "Reserved". Each one of them is 32 bits
>> long and the description of the first one is "Reserved"
>> while the description of the second reserved component is "Offset for
>> alignment".
> 
> 
> The IBTA has published errata to the 1.2.1 specification which includes the use of many reserved fields.
> 
> I believe these errata are public on their web site.
> 
> Ira
> 
>>
>> However, in the file "include/rdma/ib_sa.h" where the component mask bits for
>> the Path Records are defined, the 1st and 2nd component are combined
>> together under the name IB_SA_PATH_REC_SERVICE_ID.
>>
>>
>> #define IB_SA_PATH_REC_SERVICE_ID   (IB_SA_COMP_MASK( 0) |\
>>                                      IB_SA_COMP_MASK( 1))
>>
>>
>> The same definition exists in the OpenSM code in file "include/iba/ib_types.h"
>>
>>
>> /* Path Record Component Masks */
>> #define  IB_PR_COMPMASK_SERVICEID_MSB
>> (CL_HTON64(((uint64_t)1)<<0))
>> #define  IB_PR_COMPMASK_SERVICEID_LSB     (CL_HTON64(((uint64_t)1)<<1))
>> .....
>> .....
>> #define  IB_PR_COMPMASK_SERVICEID (IB_PR_COMPMASK_SERVICEID_MSB |
>> \
>>                                    IB_PR_COMPMASK_SERVICEID_LSB)
>>
>>
>> Why are these fields named as "SERVICE_ID"? I would expect something like
>> IB_SA_PATH_REC_RESERVED_1 and IB_SA_PATH_REC_RESERVED_2 according
>> to the specs. Are they really reserved or used, and if they are used, when does
>> this happen?
>>
>> Vangelis
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      parent reply	other threads:[~2014-08-25 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25  8:44 Are the PathRecord reserved components really reserved? Vangelis Tasoulas
     [not found] ` <53FAF771.407-S8y2klWGCOFhl2p70BpVqQ@public.gmane.org>
2014-08-25 14:49   ` Weiny, Ira
     [not found]     ` <2807E5FD2F6FDA4886F6618EAC48510E0CAD282C-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-25 20:27       ` Vangelis Tasoulas [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=53FB9C30.2000904@simula.no \
    --to=vangelis-s8y2klwgcofhl2p70bpvqq@public.gmane.org \
    --cc=ira.weiny-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