From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wipro-blr-out01.wipro.com (wipro-blr-out01.wipro.com [203.91.198.74]) by dpdk.org (Postfix) with ESMTP id D7D789584 for ; Wed, 6 Jan 2016 13:40:23 +0100 (CET) X-AuditID: cb5bdd57-f797d6d000006569-51-568d0b35168a X-Invalid-Recipients: Received: from BLR-OUT-EDG01.wipro.com ( [203.91.193.61]) by wipro-blr-out01.wipro.com (Symantec Mail Security) with SMTP id 89.0E.25961.53B0D865; Wed, 6 Jan 2016 18:10:21 +0530 (IST) Received: from BLR-EC-MBX8.wipro.com (10.208.51.118) by BLR-OUT-EDG01.wipro.com (203.91.193.31) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 6 Jan 2016 18:10:17 +0530 Received: from wipro-blr-tls01.wipro.com (203.91.193.64) by BLR-EC-MBX8.wipro.com (10.208.51.118) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 6 Jan 2016 18:10:15 +0530 Received: from APC01-SG2-obe.outbound.protection.outlook.com (65.55.88.244) by wipro-blr-tls01.wipro.com (203.91.193.64) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 6 Jan 2016 18:10:15 +0530 Received: from KL1PR03MB1784.apcprd03.prod.outlook.com (10.165.205.22) by KL1PR03MB1781.apcprd03.prod.outlook.com (10.165.205.19) with Microsoft SMTP Server (TLS) id 15.1.361.13; Wed, 6 Jan 2016 12:40:13 +0000 Received: from KL1PR03MB1784.apcprd03.prod.outlook.com ([10.165.205.22]) by KL1PR03MB1784.apcprd03.prod.outlook.com ([10.165.205.22]) with mapi id 15.01.0361.006; Wed, 6 Jan 2016 12:40:13 +0000 From: To: Thread-Topic: [dpdk-dev] Traffic scheduling in DPDK Thread-Index: AdFG/QsJlgdPYOINQVO+1njJf7gVWAAB2hlAAB71c6AAB0PH4AA4Vjbg Date: Wed, 6 Jan 2016 12:40:13 +0000 Message-ID: References: <54CBAA185211B4429112C315DA58FF6DD9EBBF@IRSMSX103.ger.corp.intel.com> <54CBAA185211B4429112C315DA58FF6DD9EE8C@IRSMSX103.ger.corp.intel.com> In-Reply-To: <54CBAA185211B4429112C315DA58FF6DD9EE8C@IRSMSX103.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=ravulakollu.kumar@wipro.com; x-originating-ip: [203.91.215.217] x-microsoft-exchange-diagnostics: 1; KL1PR03MB1781; 5:HNRJhrHOwuVHC8YFqRa775nHHgB9+HeuI/iqoaDhEp83kET8JABJjbENgIM6Icg+uWuJKIvV4IZoKa/WkBQ4T3DDUYCQ+hpZa4A+ynFB69b1qX//vvku4MzNNTCUfRELuWWKJZvr3L6iRP/U+/iO2Q==; 24:hWIsO64PhwrLDx/ZWI2FVADRu0kfb51MVrG6Zvohq6WDHTUiQGjFryV5UC7glPNenDnyC0we1+tTv9esUsKxofejUJVj7A4wMcbLVvrh45Q= x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(42140001); SRVR:KL1PR03MB1781; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(62627912741753); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(5005006)(520078)(8121501046)(3002001)(10201501046)(61426038)(61427038); SRVR:KL1PR03MB1781; BCL:0; PCL:0; RULEID:; SRVR:KL1PR03MB1781; x-forefront-prvs: 0813C68E65 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(164054003)(199003)(13464003)(189002)(377454003)(5003600100002)(1220700001)(586003)(11100500001)(101416001)(122556002)(1096002)(86362001)(15974865002)(5002640100001)(97736004)(102836003)(50986999)(40100003)(33656002)(5004730100002)(15395725005)(74316001)(93886004)(66066001)(3846002)(76176999)(15975445007)(81156007)(2950100001)(105586002)(106356001)(10400500002)(5001960100002)(5008740100001)(87936001)(54356999)(6116002)(110136002)(92566002)(19580405001)(189998001)(19580395003)(77096005)(4326007)(5890100001)(2900100001)(76576001)(18886075002); DIR:OUT; SFP:1101; SCL:1; SRVR:KL1PR03MB1781; H:KL1PR03MB1784.apcprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: wipro.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Jan 2016 12:40:13.4669 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 258ac4e4-146a-411e-9dc8-79a9e12fd6da X-MS-Exchange-Transport-CrossTenantHeadersStamped: KL1PR03MB1781 X-OrganizationHeadersPreserved: KL1PR03MB1781.apcprd03.prod.outlook.com X-CrossPremisesHeadersPromoted: BLR-HES-EDG03.wipro.com X-CrossPremisesHeadersFiltered: BLR-HES-EDG03.wipro.com X-CFilter-Loop: Reflected 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:40:24 -0000 Thanks Jasvinder, Does this application works on systems with multiple NUMA Nodes ? Thanks, Uday -----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 Hi Uday, > > 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 100= 0000 > 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 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 > > 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 ma= y contain proprietary, confidential or privileged information. If you are n= ot the intended recipient, you should not disseminate, distribute or copy t= his e-mail. Please notify the sender immediately and destroy all copies of = this message and any attachments. WARNING: Computer viruses can be transmit= ted via email. The recipient should check this email and any attachments fo= r the presence of viruses. The company accepts no liability for any damage = caused by any virus transmitted by this email. www.wipro.com