From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: [PATCH 1/3] rdma_cm: Add support for a new RDMA_PS_LUSTRE Lustre port space Date: Thu, 21 Jan 2010 11:12:08 +0200 Message-ID: <4B581A68.500@Voltaire.com> References: <20100113154952.0f01aa1d@frecb007965> <20100113155150.59867f40@frecb007965> <7ED07283D76C422C9210FBE7C832731B@amr.corp.intel.com> <20100114135815.69d5a9a5@frecb007965> <20100115084102.2258eba8@frecb007965> <20100120085530.5d675ef8@frecb007965> <4B56B8E3.3010909@voltaire.com> <20100120101717.60d733e3@frecb007965> <4B572099.3030604@Voltaire.com> <20100121092840.7429e81f@frecb007965> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100121092840.7429e81f@frecb007965> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: sebastien dugue Cc: linux-rdma , Sasha Khapyorsky List-Id: linux-rdma@vger.kernel.org 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}. Or. -- 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