[ofa-general] Re: [PATCH 3/7 V2] osm: QoS policy C & H files

[Eitan Zahavi]

Now I get you.
OK we will add this info about IPoIB CM to the RFC.

Eitan Zahavi


> -----Original Message-----
> From: Hal Rosenstock [mailto:hal.rosenstock at gmail.com] 
> Sent: Tuesday, August 28, 2007 9:42 PM
> To: Michael S. Tsirkin
> Cc: Eitan Zahavi; Yevgeny Kliteynik; OpenIB
> Subject: Re: [ofa-general] Re: [PATCH 3/7 V2] osm: QoS policy 
> C & H files
> 
> On 8/28/07, Michael S. Tsirkin <mst at dev.mellanox.co.il> wrote:
> > > >
> > > > > > Also, there was a previous question on the list on IPoIB CM 
> > > > > > relative to QoS which I either missed the answer to or was 
> > > > > > left unanswered:
> > > > > > How is IPoIB CM dealt with in terms of QoS ? Is it 
> like IPoIB UD ?
> > > > > IPoIB CM uses a specific ServiceID.
> > > >
> > > > Isn't it a range of Service IDs ?
> >
> > Yes. Service ID includes the UD QPN.
> 
> Given the limited predictability of the QPN, this would need 
> to be reflected in the QoS policy when specifying ServiceIDs 
> for IPoIB CM.
> 
> > > > > It uses CMA so it does not need any change...
> > > >
> > > > Doesn't it use CM rather than CMA ?
> >
> > Yes.
> >
> > > For more detailed info need to ask MST...
> >
> > It's all in the spec, really.
> 
> but I don't think that includes how it relates to QoS and 
> specifically the QoS policy being used by OpenSM. My point 
> was that the original defining document for OpenSM QoS policy 
> needs to be updated as I suspect it will be a source document 
> going forward that should be placed in the management git tree.
> 
> -- Hal
> 
> > --
> > MST
> >
>