Re: [Patch opensm] Allow for easily configuring multiple fabrics on one opensm server

[Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>]

On 3/5/2012 10:28 AM, Doug Ledford wrote:
> ----- Original Message -----
>> On 3/1/2012 8:31 AM, Doug Ledford wrote:
>>> I would say we are simply getting to the point where we *know* we
>>> need
>>> opensm to handle more than one fabric from a single instance ;-)
>>
>> Why does a single OpenSM need to handle multiple subnets/fabrics ?
>> What's the issue with running multiple OpenSMs with each handling
>> it's
>> own subnet/fabric ?
> 
> Because it wasn't built with the idea in mind of sharing logs or cache
> directories, etc.  

Yes, each instance has it's own configuration and output files.

> Not to mention that the proliferation of files when
> you start multiple instances of opensm is pretty insane (have you
> counted how many different files opensm can be configured to require
> now a days...).

I'm not disagreeing with the fact that there are numerous config files
(the main config file is already large enough without the myriad of
features with their own separate config files) but different subnets
have totally different configuration requirements. It's not just the
subnet prefix, SM priority, and the few other config items that you
identified.

So what would make this better in your mind ?

-- Hal
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html