From: Eli Dorfman <dorfman.eli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org
Cc: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>,
Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Hal Rosenstock
<hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: opensm: suggestion to define new common port_groups file
Date: Wed, 3 Feb 2010 17:55:21 +0200 [thread overview]
Message-ID: <694d48601002030755g5a567e78o56dd53151442607@mail.gmail.com> (raw)
In-Reply-To: <4B694919.1000207-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On Wed, Feb 3, 2010 at 11:59 AM, Yevgeny Kliteynik
<kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> wrote:
> On 03/Feb/10 11:43, Eli Dorfman (Voltaire) wrote:
>>
>> Currently there is a duplication of port group definition in OpenSM
>> configuration files.
>> Using a single configuration file for port groups will make it easier to
>> manage and will allow using group name as keyword in other configuration
>> files (i.e. partitions.conf, qos-policy.conf and opensm.conf)
>>
>> The suggested format for port-groups.conf is a simple list:
>> GroupA: GUID1, GUID2, GUID3
>> GroupB: GUID4, GUID5, GUID6
>>
>> All configuration files shall still support the old format (of specifying
>> GUIDs explicitly) and will also recognize the new Groups.
>
> I'm all for it!
>
>>
>> Following an example of partitions.conf file with new group definition:
>> management=0x7fff,ipoib,defmember=full: GroupA=full, GroupB=limited,
>> ALL_CAS=limited;
>>
>> and qos-policy.conf with the new group definition:
>>
>> port-groups
>> port-group
>> port-guid: GroupA, GroupB
>> name: my.group
>> end-port-group
>> end-port-groups
>
> Perhaps in qos-policy.conf we should be able to reference
> GroupA and GroupB directly by its name, w/o the need to
> create additional group like it is shown in the example.
We can start with the simple suggestion as shown in the example and
then enhance as you suggest.
>
> Ideally, port-groups.conf parser should be able to
> understand various keywords, such as what is used in
> partitions.conf (ALL, SWITCHES, SELF, etc).
>
> To complicate port-groups.conf parser a bit more, it would
> be nice if it could support nested definition of port groups.
>
> But no need to do it right away, we can start with something
> simple.
I agree.
Eli
>
> -- Yevgeny
>
>>
>> Thanks,
>> Eli
>> --
>> 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
>>
>
>
--
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
prev parent reply other threads:[~2010-02-03 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 9:43 opensm: suggestion to define new common port_groups file Eli Dorfman (Voltaire)
[not found] ` <4B69453E.4080701-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-02-03 9:59 ` Yevgeny Kliteynik
[not found] ` <4B694919.1000207-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-02-03 15:55 ` Eli Dorfman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=694d48601002030755g5a567e78o56dd53151442607@mail.gmail.com \
--to=dorfman.eli-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).