public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Céline Bourde" <celine.bourde-6ktuUTfB/bM@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: qos on service-id
Date: Mon, 23 Nov 2009 11:09:40 +0100	[thread overview]
Message-ID: <4B0A5F64.1030107@bull.net> (raw)
In-Reply-To: <4B0A4C71.5080209-6ktuUTfB/bM@public.gmane.org>

My /var/log/opensm.log output:

Nov 20 14:33:58 824870 [9C8566F0] 0x02 -> osm_vendor_init: 1000 pending 
umads specified
Nov 20 14:33:58 825157 [9C8566F0] 0x80 -> Entering DISCOVERING state
Using default GUID 0x2c9000100d00056d
Loading Cached Option:qos_max_vls = 8
Loading Cached Option:qos_high_limit = 1
Loading Cached Option:qos_vlarb_high = 0:1,1:0,2:0,3:0,4:0
Loading Cached Option:qos_vlarb_low = 0:1,1:2,2:4,3:8,4:0,5:32
Loading Cached Option:qos_sl2vl = 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
Entering MASTER state

Nov 20 14:33:58 840416 [9C8566F0] 0x02 -> osm_vendor_bind: Binding to 
port 0x2c9000100d00056d
Nov 20 14:33:58 877496 [9C8566F0] 0x02 -> osm_vendor_bind: Binding to 
port 0x2c9000100d00056d
Nov 20 14:33:58 877646 [9C8566F0] 0x02 -> osm_vendor_bind: Binding to 
port 0x2c9000100d00056d
Nov 20 14:33:58 877794 [9C8566F0] 0x02 -> osm_opensm_bind: Setting IS_SM 
on port 0x2c9000100d00056d
Nov 20 14:33:58 952249 [98C4F910] 0x80 -> Entering MASTER state
Nov 20 14:33:58 952467 [98C4F910] 0x02 -> osm_qos_parse_policy_file: 
Loading QoS policy file (/etc/opensm/qos-policy.conf)
Nov 20 14:33:59 047411 [9824E910] 0x01 -> sm_mad_ctrl_rcv_callback: ERR 
3111: Error status = 0x1C
Nov 20 14:33:59 047894 [9824E910] 0x01 -> SMP dump:
                                base_ver................0x1
                                mgmt_class..............0x81
                                class_ver...............0x1
                                method..................0x81 (SubnGetResp)
                                D bit...................0x1
                                status..................0x1C
                                hop_ptr.................0x0
                                hop_count...............0x2
                                trans_id................0x18ef
                                attr_id.................0x17 
(SLtoVLMappingTable)
                                resv....................0x0
                                attr_mod................0x0
                                m_key...................0x0000000000000000
                                dr_slid.................65535
                                dr_dlid.................65535

                                Initial path: 0,1,31
                                Return path:  0,22,1
                                Reserved:     [0][0][0][0][0][0][0]

                                01 23 45 67 01 23 45 6F   00 00 00 00 00 
00 00 00

                                00 00 00 00 00 00 00 00   00 00 00 00 00 
00 00 00

                                00 00 00 00 00 00 00 00   00 00 00 00 00 
00 00 00

                                00 00 00 00 00 00 00 00   00 00 00 00 00 
00 00 00


Céline Bourde a écrit :
> Hi,
>
> I'm trying to configure qos-policy.donc file for service-id use.
> I've tried basic RDMA_PS_TCP service-id level with service id 0x0106
>
> []# cat /etc/opensm/qos-policy.conf
> qos-levels
>      qos-level
>      name: DEFAULT
>      sl: 0
>      end-qos-level
>      qos-level
>          name: TCP
>          sl: 4
>      end-qos-level
>        qos-level
>           name: MPI
>           sl: 5
>       end-qos-level
> end-qos-levels
>
> qos-ulps
>  default                       : 0 # default SL
>  any, service-id 0x0000000001060000- 0x000000000106FFFF : 4
> end-qos-ulps
>
> I add this rule in my configuration and check by mapping
> sl 4 on a vl with a weight of 0
>
> # QoS default options
> qos_max_vls 8
> qos_high_limit 1
> qos_vlarb_high 0:1,1:0,2:0,3:0,4:0
> qos_vlarb_low 0:1,1:2,2:4,3:8,4:0,5:32
> qos_sl2vl 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
>
> I've launched qperf on the server side
> and listen on client:
>
> j=100; for i in $(seq 0 $j) ; do /usr/bin/qperf -ri mlx4_0:1 -li mlx4_0:1
> 10.12.1.4 -sl 4 -lp 20004 rc_bw; done;
> rc_bw:
>  bw  =  0 bytes/sec
> rc_bw:
>  bw  =  0 bytes/sec
>
> j=100; for i in $(seq 0 $j) ; do /usr/bin/qperf -ri mlx4_0:1 -li mlx4_0:1
> 10.12.1.4 -sl 5 -lp 20005 rc_bw; done;
> rc_bw:
>  bw  =  3.37 GB/sec
> rc_bw:
>  bw  =  3.37 GB/sec
>
> Qperf gives me results I expected due to qos-level configuration part, 
> but no
> expected results using qperf tcp_bw, bandwith is not
> filtered/blocked by sl weight.
>
> # j=100; for i in $(seq 0 $j) ; do /usr/bin/qperf 10.12.1.4 tcp_bw; done;
> tcp_bw:
>  bw  =  923 MB/sec
> tcp_bw:
>  bw  =  935 MB/sec
>
> j=100; for i in $(seq 0 $j) ; do /usr/bin/qperf -ri mlx4_0:1 -li mlx4_0:1
> 10.12.1.4 -sl 5 -lp 20005 rc_bw; done;
> rc_bw:
>  bw  =  2.23 GB/sec
> rc_bw:
>  bw  =  2.24 GB/sec
> rc_bw:
>  bw  =  2.21 GB/sec
>
> Could you help me to understanding service-id mechanism or give me a 
> relevant
> test to test TCP service id level ?
>
> Thanks.
>
> Céline Bourde.
>
> -- 
> 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
>
>

--
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

  parent reply	other threads:[~2009-11-23 10:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23  8:48 qos on service-id Céline Bourde
     [not found] ` <4B0A4C71.5080209-6ktuUTfB/bM@public.gmane.org>
2009-11-23 10:09   ` Céline Bourde [this message]
     [not found]     ` <4B0A5F64.1030107-6ktuUTfB/bM@public.gmane.org>
2009-11-23 14:04       ` Hal Rosenstock
     [not found]         ` <f0e08f230911230604m5b33f47ax4599e634712b57e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-23 14:22           ` Céline Bourde
2009-11-23 14:25   ` Hal Rosenstock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B0A5F64.1030107@bull.net \
    --to=celine.bourde-6ktuutfb/bm@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox