[openib-general] [PATCH 0/6] osm: QoS policy parser

Yevgeny Kliteynik kliteyn at dev.mellanox.co.il
Tue Jan 23 08:21:59 PST 2007


Hi Sasha,

Sasha Khapyorsky wrote:
> On 10:46 Sun 21 Jan     , Yevgeny Kliteynik wrote:
>> Hi Sasha.
>>
>> Sasha Khapyorsky wrote:
>>> Hi Yevgeny,
>>>
>>> On 17:01 Wed 17 Jan     , Yevgeny Kliteynik wrote:
>>>> Hi Hal
>>>>
>>>> The following series of six patches implements QoS policy file parser:
>>>>
>>>> 1. QoS parser Lex file
>>>> 2. QoS parser Lex-generated c file
>>>> 3. QoS parser grammar (Yacc) file
>>>> 4. QoS parser Yacc-generated grammar c and h file
>>>> 5. QoS parser header file that defines parse tree data structures 
>>>> 6. Changes in makefiles and configure.in file for compiling QoS parser files
>>> Is there any description of proposed format and functionality?
>> The parser is based on QoS RFC sent by Eitan in May 2006, with a few
>> minor modifications. You can find the RFC here:
>> http://openib.org/pipermail/openib-general/2006-May/022336.html
> 
> This was RFC and couple of issues were discussed then. Now you are about
> implementation phase and exact format description would be desired. For
> example what "few minor modifications" are?

I'll prepare an example file with explanations.

-- Yevgeny

>>> Also what about using human readable formats?
>> To me the xml-like format in the RFC looks pretty readable.
>> It has very limited number of keywords (tags), so it's easy 
>> to follow and/or to modify.
> 
> It is your opinion, not everybody will agree with it (AFAIR this was
> discussed too during RFC).
> 
> I would not be care, but I don't know any example of really successful
> XML using for configuration purposes (especially where advanced graphical
> config editors/viewers were not used). Do you know?
> 
> Sasha
> 




More information about the general mailing list