On 04:32 Thu 30 Aug     , Yevgeny Kliteynik wrote:
> > Also, what about --enable-qos-policy build option for those who don't
> > want to include this in their build ?
> 
>  Do you mean  permanently, or just until the new QoS will be stable?
>  Note that if someone gets ofed rpm, he gets the generated files in this
>  rpm, so he doesn't need les or yacc, so this option would be useful only
>  for machines that have git but don't have lex or yacc.
>  Do you think it's a real issue?

It is not related to lex or yacc. Some users will want to run OpenSM on
machines with limited resources and will like to strip it in size, when
QoS is not planned for use, some 50+K could be stripped:

   text    data     bss     dec     hex filename
   5820      21       0    5841    16d1 opensm-osm_qos.o
  16722      25      96   16843    41cb opensm-osm_qos_parser_l.o
  21319      28      24   21371    537b opensm-osm_qos_parser_y.o
  10782      21       0   10803    2a33 opensm-osm_qos_policy.o

I'm not sure what default should be, but to have such
--enable/disable-qos config option would be useful.

Sasha
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

Reply via email to