[ofa-general] Re: rate assignment for path queries

[Sasha Khapyorsky]

Hi Or,

On 09:20 Thu 13 Nov     , Or Gerlitz wrote:
> 
> If opensm doesn't have a match on any qos-assignment rule (eg when there's
> no qos-config file), when coming to serve sa path query,  my understanding
> is that the "qos related fields" of the partition would be used.
> 
> For example, I have set the following partition config file which assigns
> <sl=1,rate=2> to the 0x8001 partition, and run without any qos file.
> 
> Default=0x7fff,ipoib : ALL=full;
> RED=0x8001, ipoib, sl=1, rate=2, defmember=full : ALL=full;
> RED=0x8002, ipoib, sl=2, rate=3, defmember=full : ALL=full;
> 
> When a path query is issued, Indeed sl=1 is returned but I see that a
> rate=6 (20Gbs) is returned where I configured rate=2 (2.5 Gbs).

For my best knowledge rate=2 in partition config file will be related to
corresponded IPoIB multicast group for this partition, and not to
PathRecord. In PathRecord you get maximum available rate on the
requested path.

> Have I done anything wrong? is it a known issue? what does it means
> when the SM prints "min rate = 6"

Here "min rate" means minimal common rate on the path.

Sasha

> 
> Or.
> 
> 
> Nov 13 02:12:49 219374 [42803940] 0x08 -> PathRecord dump:
> 				service_id..............0x0000000000000000
> 				dgid....................0xfe80000000000000 : 0x0002c90300026be7
> 				sgid....................0xfe80000000000000 : 0x0002c90300026be3
> 				dlid....................0x0
> 				slid....................0x0
> 				hop_flow_raw............0x0
> 				tclass..................0x0
> 				num_path_revers.........0x1
> 				pkey....................0x8001
> 				qos_class...............0x0
> 				sl......................0x0
> 				mtu.....................0x3
> 				rate....................0x0
> 				pkt_life................0x0
> 				preference..............0x0
> 				resv2...................0x0
> 				resv3...................0x0
> Nov 13 02:12:49 219386 [42803940] 0x10 -> __osm_pr_rcv_check_mcast_dest: [
> Nov 13 02:12:49 219390 [42803940] 0x10 -> __osm_pr_rcv_check_mcast_dest: ]
> Nov 13 02:12:49 219394 [42803940] 0x08 -> osm_pr_rcv_process: Unicast destination requested
> Nov 13 02:12:49 219398 [42803940] 0x10 -> __osm_pr_rcv_get_end_points: [
> Nov 13 02:12:49 219403 [42803940] 0x10 -> __osm_pr_rcv_get_end_points: ]
> Nov 13 02:12:49 219407 [42803940] 0x10 -> __osm_pr_rcv_process_pair: [
> Nov 13 02:12:49 219411 [42803940] 0x10 -> __osm_pr_rcv_get_port_pair_paths: [
> Nov 13 02:12:49 219415 [42803940] 0x08 -> __osm_pr_rcv_get_port_pair_paths: Src port 0x0002c90300026be3, Dst port 0x0002c90300026be7
> Nov 13 02:12:49 219420 [42803940] 0x10 -> osm_port_share_pkey: [
> Nov 13 02:12:49 219424 [42803940] 0x10 -> osm_port_share_pkey: ]
> Nov 13 02:12:49 219428 [42803940] 0x10 -> osm_port_share_pkey: [
> Nov 13 02:12:49 219432 [42803940] 0x10 -> osm_port_share_pkey: ]
> Nov 13 02:12:49 219436 [42803940] 0x10 -> osm_port_share_pkey: [
> Nov 13 02:12:49 219440 [42803940] 0x10 -> osm_port_share_pkey: ]
> Nov 13 02:12:49 219444 [42803940] 0x08 -> __osm_pr_rcv_get_port_pair_paths: Src LIDs [0x7-0x7], Dest LIDs [0x8-0x8]
> Nov 13 02:12:49 219449 [42803940] 0x10 -> __osm_pr_rcv_get_lid_pair_path: [
> Nov 13 02:12:49 219453 [42803940] 0x08 -> __osm_pr_rcv_get_lid_pair_path: Src LID 0x7, Dest LID 0x8
> Nov 13 02:12:49 219458 [42803940] 0x10 -> __osm_pr_rcv_get_path_parms: [
> Nov 13 02:12:49 219464 [42803940] 0x08 -> __osm_pr_rcv_get_path_parms: Path min MTU = 4, min rate = 6
> Nov 13 02:12:49 219471 [42803940] 0x08 -> __osm_pr_rcv_get_path_parms: Path params: mtu = 4, rate = 6, packet lifetime = 18, pkey = 0x8001, sl = 1
> Nov 13 02:12:49 219476 [42803940] 0x10 -> __osm_pr_rcv_get_path_parms: ]
> Nov 13 02:12:49 219480 [42803940] 0x10 -> __osm_pr_rcv_get_path_parms: [
> Nov 13 02:12:49 219484 [42803940] 0x08 -> __osm_pr_rcv_get_path_parms: Path min MTU = 4, min rate = 6
> Nov 13 02:12:49 219489 [42803940] 0x08 -> __osm_pr_rcv_get_path_parms: Path params: mtu = 4, rate = 6, packet lifetime = 18, pkey = 0x8001, sl = 1