On Thu, 21 Jan 2010 11:12:08 +0200
Or Gerlitz <ogerl...@voltaire.com> wrote:
> sebastien dugue wrote:
> > OK, then going with the TCP port space, what we need in OpenSM is a
> > combination of service id (TCP) _and_ TCP port _and_ target GUID.
>
> I believe that you can have a 'lustre' keyword in opensm qos parser which
> stands for the combination of tcp port space + lustre tcp port (maybe it
> exists now), so in the policy file this would translate to X,{Z1,Z2,..,Zm}
> (as was in your example) and not to X,Y,{Z1,Z2,..,Zm}.
Right, that'd be a nice shortcut. I also think being able to specify both port
and target GUID to the TCP port space might be interesting for other ULPs, not
just Lustre.
Sebastien.
>
> Or.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majord...@vger.kernel.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 majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
