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

[Sasha Khapyorsky]

Hi Eitan,

On 10:30 Tue 28 Aug     , Eitan Zahavi wrote:
> 
> As you pointed out, coming up with a VLArb and SL2VL manager that is
> supporting both routing and QoS is not trivial.
> But even with a uniform and statically assigned tables (supported by the
> current options config file) different QoS classes can be provided to
> different clients by the new QoS policy code.

It leaves an user in the state when using QoS requires manual
configuration of two different in capabilities and potentially
conflicting QoS managers.

> I agree our OFED 1.3 is somewhat limited as it does not solve the VLArb
> and SL2VL setting issue.
> But with the time constrains of the development, review and QA this is
> the most we could do for 1.3

This feature was mentioned as requirement couple of times even at
beginning of 1.2 days.

There are extra 7 days now up to feature freeze. Also QoS is optional,
and in part of VLArb and SL2VL setup the risk of affecting other OpenSM
components is relatively low. OTOH it is very important to have full
functional and integrated QoS. So basically I'm fine to review such
patches even after feature freeze date (not in the last RC day of course
:)).

Sasha