From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id ABCC69254 for ; Tue, 5 Jan 2016 11:10:00 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP; 05 Jan 2016 02:09:59 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,524,1444719600"; d="scan'208";a="874861000" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by fmsmga001.fm.intel.com with ESMTP; 05 Jan 2016 02:09:58 -0800 Received: from irsmsx112.ger.corp.intel.com (10.108.20.5) by IRSMSX101.ger.corp.intel.com (163.33.3.153) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 5 Jan 2016 10:09:57 +0000 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.143]) by irsmsx112.ger.corp.intel.com ([10.108.20.5]) with mapi id 14.03.0248.002; Tue, 5 Jan 2016 10:09:57 +0000 From: "Singh, Jasvinder" To: "ravulakollu.kumar@wipro.com" Thread-Topic: [dpdk-dev] Traffic scheduling in DPDK Thread-Index: AdFG/QsJlgdPYOINQVO+1njJf7gVWAAB2hlAAB71c6AAB0PH4A== Date: Tue, 5 Jan 2016 10:09:56 +0000 Message-ID: <54CBAA185211B4429112C315DA58FF6DD9EE8C@IRSMSX103.ger.corp.intel.com> References: <54CBAA185211B4429112C315DA58FF6DD9EBBF@IRSMSX103.ger.corp.intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMjQyMTFiZTktNTU1Ny00ZTk4LTkyYjUtMzQ5MmU0MzQ5YmMyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX1BVQkxJQyJ9XX1dfSwiU3ViamVjdExhYmVscyI6W10sIlRNQ1ZlcnNpb24iOiIxNS40LjEwLjE5IiwiVHJ1c3RlZExhYmVsSGFzaCI6IllmdEVRZ2J3TDY5ekNERFNWamdOdHc2Y1NWTVwvZWxJR2VJcHBhQlNEYlwvRT0ifQ== x-ctpclassification: CTP_PUBLIC x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Traffic scheduling in DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2016 10:10:01 -0000 Hi Uday, >=20 > Thanks Jasvinder , I am running the below command >=20 > ./build/qos_sched -c 0xe -n 1 -- --pfc "0,1,3,2" --cfg ./profile.cfg >=20 > Bound two 1G physical ports to DPDK , and started running the above > command with the default profile mentioned in profile.cfg . > I am using lcore 3 and 2 for RX and TX. It was not successful, getting th= e > below error. >=20 > APP: Initializing port 0... PMD: eth_igb_rx_queue_setup(): > sw_ring=3D0x7f5b20ba2240 hw_ring=3D0x7f5b20ba2680 dma_addr=3D0xbf87a2680 > PMD: eth_igb_tx_queue_setup(): To improve 1G driver performance, > consider setting the TX WTHRESH value to 4, 8, or 16. > PMD: eth_igb_tx_queue_setup(): sw_ring=3D0x7f5b20b910c0 > hw_ring=3D0x7f5b20b92100 dma_addr=3D0xbf8792100 > PMD: eth_igb_start(): << > done: Link Up - speed 1000 Mbps - full-duplex > APP: Initializing port 1... PMD: eth_igb_rx_queue_setup(): > sw_ring=3D0x7f5b20b80a40 hw_ring=3D0x7f5b20b80e80 dma_addr=3D0xbf8780e80 > PMD: eth_igb_tx_queue_setup(): To improve 1G driver performance, > consider setting the TX WTHRESH value to 4, 8, or 16. > PMD: eth_igb_tx_queue_setup(): sw_ring=3D0x7f5b20b6f8c0 > hw_ring=3D0x7f5b20b70900 dma_addr=3D0xbf8770900 > PMD: eth_igb_start(): << > done: Link Up - speed 1000 Mbps - full-duplex > SCHED: Low level config for pipe profile 0: > Token bucket: period =3D 3277, credits per period =3D 8, size =3D 100= 0000 > Traffic classes: period =3D 5000000, credits per period =3D [12207, 1= 2207, 12207, > 12207] > Traffic class 3 oversubscription: weight =3D 0 > WRR cost: [1, 1, 1, 1], [1, 1, 1, 1], [1, 1, 1, 1], [1, 1, 1, 1] > EAL: Error - exiting with code: 1 > Cause: Unable to config sched subport 0, err=3D-2 In default profile.cfg, It is assumed that all the nic ports have 10 Gbps r= ate. The above error occurs when subport's tb_rate (10Gbps) is found more = than NIC port's capacity (1 Gbps). Therefore, you need to use either 10 Gbp= s ports in your application or have to amend the profile.cfg to work with 1= Gbps port. Please refer to DPDK QoS framework document for more details = on various parameters - http://dpdk.org/doc/guides/prog_guide/qos_framework= .html > -----Original Message----- > From: Singh, Jasvinder [mailto:jasvinder.singh@intel.com] > Sent: Monday, January 04, 2016 9:26 PM > To: Ravulakollu Udaya Kumar (WT01 - Product Engineering Service); > dev@dpdk.org > Subject: RE: [dpdk-dev] Traffic scheduling in DPDK >=20 > Hi Uday, >=20 >=20 > > I have an issue in running qos_sched application in DPDK .Could > > someone tell me how to run the command and what each parameter does > > In the below mentioned text. > > > > Application mandatory parameters: > > --pfc "RX PORT, TX PORT, RX LCORE, WT LCORE" : Packet flow > configuration > > multiple pfc can be configured in command line >=20 >=20 > RX PORT - Specifies the packets receive port TX PORT - Specifies the pack= ets > transmit port RXCORE - Specifies the Core used for Packet reception and > Classification stage of the QoS application. > WTCORE- Specifies the Core used for Packet enqueue/dequeue operation > (QoS scheduling) and subsequently transmitting the packets out. >=20 > Multiple pfc can be specified depending upon the number of instances of > qos sched required in application. For example- in order to run two inst= ance, > following can be used- >=20 > ./build/qos_sched -c 0x7e -n 4 -- --pfc "0,1,2,3,4" --pfc "2,3,5,6" --cfg > "profile.cfg" >=20 > First instance of qos sched receives packets from port 0 and transmits it= s > packets through port 1 ,while second qos sched will receives packets from > port 2 and transmit through port 3. In case of single qos sched instance, > following can be used- >=20 > ./build/qos_sched -c 0x1e -n 4 -- --pfc "0,1,2,3,4" --cfg "profile.cfg" >=20 >=20 > Thanks, > Jasvinder > The information contained in this electronic message and any attachments = to > this message are intended for the exclusive use of the addressee(s) and m= ay > contain proprietary, confidential or privileged information. If you are n= ot the > intended recipient, you should not disseminate, distribute or copy this e= - > mail. Please notify the sender immediately and destroy all copies of this > message and any attachments. WARNING: Computer viruses can be > transmitted via email. The recipient should check this email and any > attachments for the presence of viruses. The company accepts no liability= for > any damage caused by any virus transmitted by this email. www.wipro.com