Re: [PATCH v3] opensm: support routing engine update

Yevgeny Kliteynik
2010-02-14T12:38:54Z

On 14/Feb/10 12:18, Eli Dorfman (Voltaire) wrote:
> Slava Strebkov wrote:
>> HI!
>> That was my misunderstanding - upon heavy sweep SM will try to load
>> routing engines as defined in the SM.conf file (ftree& updn - in that
>> order).
>> So ftree will be loaded when switch comes back from reboot.
>>
>> Slava
>>
>> -----Original Message-----
>> From: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> [mailto:linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org] On Behalf Of Yevgeny Kliteynik
>> Sent: Monday, December 07, 2009 10:22 AM
>> To: Slava Strebkov
>> Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> Subject: Re: [PATCH v3] opensm: support routing engine update
>>
>> Slava,
>>
>> Slava Strebkov wrote:
>>> Hi Yevgeny,
>>> In that case SM will use updn and will not come back to ftree
>>> automatically.
>>
>> I think that this is a bad thing.
>>
>> I wouldn't want *temporary* change of fabric to cause
>> *permanent* change of SM mode of operation. Such changes
>> do happen, and I'd prefer SM to continue functioning
>> in accordance to the user's configuration once the
>> fabric is settled again.
>>
>> I do see the cases were the change that you propose is
>> beneficial - if fabric topology doesn't fits the chosen
>> routing, SM will waste time on retrying the wrong routing
>> at every heavy sweep, but this happens due to suboptimal
>> SM configuration and not as a result of some event that
>> user has no control of.
>
> For every heavy sweep the SM will try to configure the routing engines as specified in the conf file.
> So when a switch goes up and ftree configuration is valid, the SM will configure ftree instead of updn.

OK then, sounds good.