From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id AF80995A6 for ; Wed, 6 Jan 2016 13:57:12 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP; 06 Jan 2016 04:57:13 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,529,1444719600"; d="scan'208";a="875638431" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by fmsmga001.fm.intel.com with ESMTP; 06 Jan 2016 04:57:10 -0800 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.143]) by IRSMSX102.ger.corp.intel.com ([169.254.2.131]) with mapi id 14.03.0248.002; Wed, 6 Jan 2016 12:57:09 +0000 From: "Singh, Jasvinder" To: "ravulakollu.kumar@wipro.com" Thread-Topic: [dpdk-dev] Traffic scheduling in DPDK Thread-Index: AdFG/QsJlgdPYOINQVO+1njJf7gVWAAB2hlAAB71c6AAB0PH4AA4VjbgAAC7h4A= Date: Wed, 6 Jan 2016 12:57:09 +0000 Message-ID: <54CBAA185211B4429112C315DA58FF6DDA028C@IRSMSX103.ger.corp.intel.com> References: <54CBAA185211B4429112C315DA58FF6DD9EBBF@IRSMSX103.ger.corp.intel.com> <54CBAA185211B4429112C315DA58FF6DD9EE8C@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: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzFiOTg3YmMtMjZlYi00ZDZhLTgxYTQtMTcwODI5MjE2MGU4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiZTdnN0FicHlKeE5ESGo2S09QTk9JdkJxS3hDaEhWMlB1QnRoXC9aUDdMR1k9In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] 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: Wed, 06 Jan 2016 12:57:13 -0000 > -----Original Message----- > From: ravulakollu.kumar@wipro.com [mailto:ravulakollu.kumar@wipro.com] > Sent: Wednesday, January 6, 2016 12:40 PM > To: Singh, Jasvinder > Cc: dev@dpdk.org > Subject: RE: [dpdk-dev] Traffic scheduling in DPDK >=20 > Thanks Jasvinder, >=20 > Does this application works on systems with multiple NUMA Nodes ? >=20 It does.=20 > Thanks, > Uday >=20 > -----Original Message----- > From: Singh, Jasvinder [mailto:jasvinder.singh@intel.com] > Sent: Tuesday, January 05, 2016 3:40 PM > To: Ravulakollu Udaya Kumar (WT01 - Product Engineering Service) > Cc: dev@dpdk.org > Subject: RE: [dpdk-dev] Traffic scheduling in DPDK >=20 > Hi Uday, >=20 > > > > Thanks Jasvinder , I am running the below command > > > > ./build/qos_sched -c 0xe -n 1 -- --pfc "0,1,3,2" --cfg ./profile.cfg > > > > 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 > > the below error. > > > > 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 1= 000000 > > Traffic classes: period =3D 5000000, credits per period =3D [12207, > > 12207, 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 >=20 >=20 > In default profile.cfg, It is assumed that all the nic ports have 10 Gbps= rate. > The above error occurs when subport's tb_rate (10Gbps) is found more tha= n > NIC port's capacity (1 Gbps). Therefore, you need to use either 10 Gbps p= orts > 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 >=20 >=20 > > -----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 > > > > Hi Uday, > > > > > > > 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 > > > > > > RX PORT - Specifies the packets receive port TX PORT - Specifies the > > packets 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. > > > > Multiple pfc can be specified depending upon the number of instances > > of qos sched required in application. For example- in order to run > > two instance, following can be used- > > > > ./build/qos_sched -c 0x7e -n 4 -- --pfc "0,1,2,3,4" --pfc "2,3,5,6" > > --cfg "profile.cfg" > > > > First instance of qos sched receives packets from port 0 and transmits > > its 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- > > > > ./build/qos_sched -c 0x1e -n 4 -- --pfc "0,1,2,3,4" --cfg "profile.cfg" > > > > > > 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 may contain proprietary, confidential or privileged > > information. If you are not 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 > 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