From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Khapyorsky Subject: Re: [PATCH] opensm/osm_qos.c: merge SL2VL mapping capability check Date: Mon, 25 Jan 2010 17:20:18 +0200 Message-ID: <20100125152018.GO13519@me> References: <20091201194110.GA26753@comcast.net> <20100104170141.GK26940@me> <20100112103517.GI26089@me> <20100116202759.GA574@me> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Hal Rosenstock Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-rdma@vger.kernel.org On 07:25 Sat 23 Jan , Hal Rosenstock wrote: > >> > >> It does. There's a requirement that SL2VL mapping is required when VLCap > 1. > > > > Correct, I found it in o7-4. Basically we can check both (now after > > switch/endport separation in the code this should be easier), but I > > would prefer to understand better an issue (if we have) first. > > > > Also same o7-4 is applicable to CA and router ports. > > I see no mention of CA and router ports in o7-4. This is the point. o7-4 is not limited by switch ports. > What are you > referring to here ? This was the question, why such capability check should be (was) ideologically different for CA ports? If 'VLCap > 1' is significant capability indication for switch ports this should be the same interpretation with CA and router ports. > > > Do you know why > > was VLCap > 1 condition ignored there? > > Where is the "there" that you are referring to above ? not switch ports. Sasha -- 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