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: Wed, 20 Jan 2010 10:03:47 +0200 Message-ID: <4B56B8E3.3010909@voltaire.com> References: <20100113154952.0f01aa1d@frecb007965> <20100113155150.59867f40@frecb007965> <7ED07283D76C422C9210FBE7C832731B@amr.corp.intel.com> <20100114135815.69d5a9a5@frecb007965> <20100115084102.2258eba8@frecb007965> <20100120085530.5d675ef8@frecb007965> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20100120085530.5d675ef8@frecb007965> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: sebastien dugue Cc: Roland Dreier , Sean Hefty , linux-rdma , Roland Dreier , Sasha Khapyorsky List-Id: linux-rdma@vger.kernel.org sebastien dugue wrote: >> So I guess you need to change the ports used within the new port spa= ce -- but then=20 >> why can't you just stay in the TCP space but change the ports used? >> =20 > > No, with the new port space, there's no need to change ports. You onl= y need to specify the target GUIDs. For example: > lustre, target-=C2=ADport=C2=ADguid 0x1234,0x1235 : 1 # lustr= e traffic to MDSs > lustre : 2 # default lustre traffic (= to OSSs) > Hope this helps clarify things a bit. > =20 sorry, but it doesn't, as far as I understand there are three=20 possibilities for what the string "lustre" is being translated to by the opensm QoS logic: (A) lustre port in the TCP port space (B) lustre port space (C) nothing (that is not a service, in the same manner that ipoib just=20 doesn't mean anything to opensm) Assuming C is not the case, then either A or B will yield the same=20 result and as such the new port space buys you nothing. Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" i= n the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html