[openib-general] [PATCH 0/10] osm: QoS in OpenSM

[Yevgeny Kliteynik]

Hi Hal,

Hal Rosenstock wrote:
> Hi Yevgeny,
> 
> On Tue, 2007-01-30 at 09:51, Yevgeny Kliteynik wrote:
>> Hi Hal.
>>
>> The following is a series of 10 patches:
>> 1. QoS policy file parser Yacc file
>> 2. QoS policy file parser Lex file
>> 3. QoS policy file parser Yacc & Lex generated files
>> 4. QoS policy file parser header file
>> 5. QoS policy file parser C file with auxiliary functions
>> 6. Compilation changes for QoS policy file parser:
>>    Added new files to makefiles.
>>    Introduced new configuration switch '--enable-maintainer-mode',
>>    which will run Lex & Yacc instead of just using the generated
>>    files.
>> 7. Renamed static function find_prtn_by_name() to non-static osm_prtn_find_by_name()
>>    This function will be used later by the PathRecord logic.
>> 8. Added QoS class and service id fields to the path record.
>> 9. Added new command line option for OSM: '-Y' or '--qos_policy_file'
>> 10.Checking PathRecord query for QoS constraints.
> 
> Is everyone on the list satisfied with an XML format or should there be
> a text version ? Is anyone concerned about the ease of configuring XML
> for QoS ?
> 
> IMO, the XML syntax needs to be explained, discussed, and vetted on the
> list. I am hopping this can occur reasonably quickly. If we are doing
> XML for this, we need to get to a stable agreed syntax.
> 
> A couple of missing minor things:
> SA ClassPortInfo and SA MultiPathRecord similar to PathRecord
> 
> A major missing component is a QoS manager which supports the granular
> configuration of the SL2VL and VLArb tables. Based on our experience
> with the existing QoS manager, this effort is not to be minimized. If
> this is not part of this package, a fair portion of the QoS syntax is
> "dormant". I know this can be run on top of the existing QoS manager to
> get a more complete QoS solution than what already exists so this could
> be considered an stepping stone towards that.
> 

I already started working on multipath, and the next item on my list is 
QoS manager (or QoS setup), but I seriously doubt that I will manage to
finish it till the feature freeze, which is today :)
Anyway, qos policy file parser (whatever the format is) and the PathRecord
are definitely a stepping stone towards full QoS support in OpenSM.

-- Yevgeny

> -- Hal
> 
>> --
>> Yevgeny
>>
>> Signed-off-by:  Yevgeny Kliteynik <kliteyn at dev.mellanox.co.il>
>>  
>>
>>
>