Re: IPoIB TC MIB

"Hal Rosenstock" <[email protected]> Tue, 20 Dec 2005 11:26:23 -0500
Newsgroups gmane.ietf.ipoib
Message-ID <[email protected]>
This is a multi-part message in MIME format.

--===============0538217771==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0050_01C60558.352C6280"

This is a multi-part message in MIME format.

------=_NextPart_000_0050_01C60558.352C6280
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi David,

See <hnr>...</hnr> comments embedded below.

-- Hal
  ----- Original Message -----=20
  From: David M. Brean=20
  To: Hal Rosenstock=20
  Cc: IPoverIB=20
  Sent: Tuesday, December 20, 2005 11:08 AM
  Subject: Re: [Ipoverib] IPoIB TC MIB


  Hal Rosenstock wrote:

    Hi David,

    Are you referring to the IBA definition of partition ?

  Yes.


    Then my quibble is with this. If full and limited members are in the =
same partition, it seems there are 2 PKeys for the partition (and look =
at the valuie range for ibPartitionKey) so my comment is then as =
follows:


  Yes, there are two different 16-bit P_Keys that can be used by ports =
communicating in the same partition.

  <hnr> Understood. </hnr>

    While ibPartition is a 16 bit value, it is filled with the low 15 =
bits of the PKey with the high bit being zero. That is not clear (and =
that is how I think it needs to be used).

    I want a partition based table (with full and limited members) not =
separate ones (for full and limited members).


  In general, I'd prefer to have the membership bit exposed since it =
impacts the communication capabilities of a port in a partition.  Also, =
I'm not sure what you mean by "not separate ones" because a P_Key table =
can store P_Keys with both full and limited membership.

  <hnr> Yes, the membership is exposed but in a different way. As to =
separate, I'm referring to the use of ibPartitionKey in the SM MIB in =
the partition table. Maybe I'm wrong but partition key is different from =
partition. It seems that there is some redundancy in that table if =
indeed the ibPartitionKey is the full 16 bits. </hnr>

  -David


    -- Hal
      ----- Original Message -----=20
      From: David M. Brean=20
      To: Hal Rosenstock=20
      Cc: IPoverIB=20
      Sent: Tuesday, December 20, 2005 4:09 AM
      Subject: Re: [Ipoverib] IPoIB TC MIB


      Hello,

      Hal Rosenstock wrote:

        Hi,

        In draft-ietf-ipoib-ibmib-tc-mib-07.txt, there is ibPartitionKey =
as follows:

IbPartitionKey ::=3D TEXTUAL-CONVENTION
    DISPLAY-HINT "x"
    STATUS      current
    DESCRIPTION
       "The 16-bit Partition Key."
    SYNTAX Unsigned32 (0..65535)How about an ibPartition with a =
definition something like the following:IbPartition ::=3D =
TEXTUAL-CONVENTION
    DISPLAY-HINT "x"
    STATUS      current
    DESCRIPTION
       "The 15-bit Partition Key Base without the membership bit."
    SYNTAX Unsigned32 (0..32767)
      A partition has full and limited members where all 16-bits define =
the partition.  In fact, text says "A collection of endnodes with the =
same P_Key in their P_Key Tables are referred to as being members of a =
partition, or in a partition. A P_Key Table can specify one of two types =
of partition membership: Limited or Full."  So, I think that you should =
choose a different name, if this is needed.  Also, how do you propose to =
use this new definition?

      By the way, a nit: the MIB also defines the "IbSmPortList".  Can =
it be called "IbSmaPortList" or "IbPortList"?  It's used in the SMA MIB.

      -David


 -- =
Hal----------------------------------------------------------------------=
--
_______________________________________________
IPoverIB mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ipoverib
  
------=_NextPart_000_0050_01C60558.352C6280
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3DISO-8859-1>
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi David,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>See &lt;hnr&gt;...&lt;/hnr&gt; comments =
embedded=20
below.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>-- Hal</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A [email protected] =
href=3D"mailto:[email protected]">David M.=20
  Brean</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
[email protected]=20
  href=3D"mailto:[email protected]">Hal Rosenstock</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
[email protected]=20
  href=3D"mailto:[email protected]">IPoverIB</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, December 20, =
2005 11:08=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [Ipoverib] IPoIB =
TC=20
MIB</DIV>
  <DIV><FONT face=3DArial size=3D2></FONT><BR></DIV>Hal Rosenstock =
wrote:<BR>
  <BLOCKQUOTE =
[email protected]=20
  type=3D"cite">
    <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
    <DIV><FONT face=3DArial size=3D2>Hi David,</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>Are you referring to the IBA =
definition of=20
    partition ?</FONT></DIV></BLOCKQUOTE><BR>Yes.<BR><BR>
  <BLOCKQUOTE =
[email protected]=20
  type=3D"cite">
    <DIV><FONT face=3DArial size=3D2>Then my quibble is with this. If =
full and=20
    limited members are in the same partition, it seems there are 2 =
PKeys for=20
    the partition (and look at the valuie range for ibPartitionKey) so=20
    m</FONT><FONT face=3DArial size=3D2>y comment is then as =
follows:</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE>
  <DIV><FONT face=3DArial size=3D2></FONT><BR>Yes, there are two =
different 16-bit=20
  P_Keys that can be used by ports communicating in the same =
partition.</DIV>
  <DIV><FONT face=3DArial size=3D2></FONT><BR><FONT face=3DArial =
size=3D2>&lt;hnr&gt;=20
  Understood. &lt;/hnr&gt;</FONT><BR></DIV>
  <BLOCKQUOTE =
[email protected]=20
  type=3D"cite">
    <DIV><FONT face=3DArial size=3D2>While ibPartition is a 16 bit =
value, it is=20
    filled with the low 15 bits of the PKey with the high bit being =
zero. That=20
    is not clear (and that is how I think it needs to be =
used).</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE>
  <BLOCKQUOTE =
[email protected]=20
  type=3D"cite">
    <DIV><FONT face=3DArial size=3D2>I want a partition based table =
(with full and=20
    limited members) not separate ones (for full and limited=20
    members).</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE>
  <DIV><FONT face=3DArial size=3D2></FONT><BR>In general, I'd prefer to =
have the=20
  membership bit exposed since it impacts the communication capabilities =
of a=20
  port in a partition.&nbsp; Also, I'm not sure what you mean by "not =
separate=20
  ones" because a P_Key table can store P_Keys with both full and =
limited=20
  membership.</DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&lt;hnr&gt; Yes, the membership is =
exposed but in=20
  a different way. As to separate, I'm referring to the use of =
ibPartitionKey in=20
  the SM MIB in the partition table. Maybe I'm wrong but partition key =
is=20
  different from partition. It seems that there is some redundancy in =
that table=20
  if indeed the ibPartitionKey is the full 16 bits. =
&lt;/hnr&gt;</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT><FONT=20
  face=3DArial size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT =
face=3DArial=20
  size=3D2></FONT><BR>-David<BR><BR></DIV>
  <BLOCKQUOTE =
[email protected]=20
  type=3D"cite">
    <DIV><FONT face=3DArial size=3D2>-- Hal</FONT></DIV>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: rgb(0,0,0) 2px solid; MARGIN-RIGHT: 0px">
      <DIV=20
      style=3D"FONT: 10pt arial; font-size-adjust: none; font-stretch: =
">-----=20
      Original Message ----- </DIV>
      <DIV=20
      style=3D"BACKGROUND: rgb(228,228,228) 0% 50%; FONT: 10pt arial; =
font-size-adjust: none; font-stretch: ; moz-background-clip: initial; =
moz-background-origin: initial; moz-background-inline-policy: =
initial"><B>From:</B>=20
      <A [email protected] =
href=3D"mailto:[email protected]">David M.=20
      Brean</A> </DIV>
      <DIV=20
      style=3D"FONT: 10pt arial; font-size-adjust: none; font-stretch: =
"><B>To:</B>=20
      <A [email protected] =
href=3D"mailto:[email protected]">Hal=20
      Rosenstock</A> </DIV>
      <DIV=20
      style=3D"FONT: 10pt arial; font-size-adjust: none; font-stretch: =
"><B>Cc:</B>=20
      <A [email protected] =
href=3D"mailto:[email protected]">IPoverIB</A>=20
      </DIV>
      <DIV=20
      style=3D"FONT: 10pt arial; font-size-adjust: none; font-stretch: =
"><B>Sent:</B>=20
      Tuesday, December 20, 2005 4:09 AM</DIV>
      <DIV=20
      style=3D"FONT: 10pt arial; font-size-adjust: none; font-stretch: =
"><B>Subject:</B>=20
      Re: [Ipoverib] IPoIB TC MIB</DIV>
      <DIV><BR></DIV><TT>Hello,</TT><BR><BR>Hal Rosenstock wrote:<BR>
      <BLOCKQUOTE =
[email protected]=20
      type=3D"cite">
        <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
        <STYLE></STYLE>

        <DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
        <DIV>&nbsp;</DIV>
        <DIV><FONT face=3DArial size=3D2>In =
draft-ietf-ipoib-ibmib-tc-mib-07.txt,=20
        there is ibPartitionKey as follows:</FONT></DIV>
        <DIV>&nbsp;</DIV>
        <DIV><!--StartFragment --><PRE>IbPartitionKey ::=3D =
TEXTUAL-CONVENTION
    DISPLAY-HINT "x"
    STATUS      current
    DESCRIPTION
       "The 16-bit Partition Key."
    SYNTAX Unsigned32 (0..65535)</PRE><PRE><FONT face=3DArial =
size=3D2>How about an ibPartition with a definition something like the =
following:</FONT></PRE><PRE><!--StartFragment --><PRE>IbPartition ::=3D =
TEXTUAL-CONVENTION
    DISPLAY-HINT "x"
    STATUS      current
    DESCRIPTION
       "The 15-bit Partition Key Base without the membership bit."
    SYNTAX Unsigned32 (0..32767)</PRE></PRE></DIV></BLOCKQUOTE><BR>A=20
      partition has full and limited members where all 16-bits define =
the=20
      partition.&nbsp; In fact, text says "A collection of endnodes with =
the=20
      same P_Key in their P_Key Tables are referred to as being members =
of a=20
      partition, or in a partition. A P_Key Table can specify one of two =
types=20
      of partition membership: Limited or Full."&nbsp; So, I think that =
you=20
      should choose a different name, if this is needed.&nbsp; Also, how =
do you=20
      propose to use this new definition?<BR><BR>By the way, a nit: the =
MIB also=20
      defines the "IbSmPortList".&nbsp; Can it be called "IbSmaPortList" =
or=20
      "IbPortList"?&nbsp; It's used in the SMA =
MIB.<BR><BR>-David<BR><BR>
      <BLOCKQUOTE =
[email protected]=20
      type=3D"cite">
        <DIV><PRE><PRE>&nbsp;</PRE><PRE><FONT face=3DArial size=3D2>-- =
Hal</FONT></PRE></PRE></DIV><PRE wrap=3D""><HR width=3D"90%" SIZE=3D4>
_______________________________________________
IPoverIB mailing list
<A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:[email protected]">[email protected]</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"https://www1.ietf.org/mailman/listinfo/ipoverib">https://www1.iet=
f.org/mailman/listinfo/ipoverib</A>
  =
</PRE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0050_01C60558.352C6280--



--===============0538217771==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPoverIB mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ipoverib

--===============0538217771==--