From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wipro-chn-out01.wipro.com (wipro-chn-out01.wipro.com [203.91.208.14]) by dpdk.org (Postfix) with ESMTP id A75DD91E3 for ; Tue, 5 Jan 2016 07:21:26 +0100 (CET) X-AuditID: cb5bdd88-f79ee6d000001534-3b-568b60e4a532 X-Invalid-Recipients: Received: from BLR-OUT-EDG01.wipro.com ( [203.91.201.88]) by wipro-chn-out01.wipro.com (Symantec Mail Security) with SMTP id 8B.D9.05428.4E06B865; Tue, 5 Jan 2016 11:51:25 +0530 (IST) Received: from BLR-EC-MBX6.wipro.com (10.208.51.116) by BLR-OUT-EDG01.wipro.com (203.91.193.31) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 5 Jan 2016 11:51:23 +0530 Received: from wipro-blr-tls01.wipro.com (203.91.193.100) by BLR-EC-MBX6.wipro.com (10.208.51.116) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 5 Jan 2016 11:51:23 +0530 Received: from APC01-SG2-obe.outbound.protection.outlook.com (65.55.88.243) by wipro-blr-tls01.wipro.com (203.91.193.100) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 5 Jan 2016 11:51:22 +0530 Received: from KL1PR03MB1784.apcprd03.prod.outlook.com (10.165.205.22) by KL1PR03MB1782.apcprd03.prod.outlook.com (10.165.205.20) with Microsoft SMTP Server (TLS) id 15.1.361.13; Tue, 5 Jan 2016 06:21:20 +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; Tue, 5 Jan 2016 06:21:20 +0000 From: To: Thread-Topic: [dpdk-dev] Traffic scheduling in DPDK Thread-Index: AdFG/QsJlgdPYOINQVO+1njJf7gVWAAB2hlAAB71c6A= Date: Tue, 5 Jan 2016 06:21:20 +0000 Message-ID: References: <54CBAA185211B4429112C315DA58FF6DD9EBBF@IRSMSX103.ger.corp.intel.com> In-Reply-To: <54CBAA185211B4429112C315DA58FF6DD9EBBF@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; KL1PR03MB1782; 5:fncl+WZz+7ab3KtCt3B3N1KF4ND1+asQOZjd4m5AS3M9yH0R6znD40mvjGgAKgNT1Mf+xvOFVelOKF/HtMqbUnk2uzwnfzWH51c/o4OldtliS9EGQfk3zibqK6UuXDtXfVMuXZpPMRAIe8pYrmKoDg==; 24:E2s3Ky6UplpVGwSuIzJAg40h5GAxtPJf/dUaLboI4EEqvH8ASjkQIAXhqVqRcsIAA3rige7I9rIHzESnyJJcY77Hf4CObM85hqo/cJlt0m4= x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(42140001); SRVR:KL1PR03MB1782; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(520078)(8121501046)(5005006)(10201501046)(3002001)(61426038)(61427038); SRVR:KL1PR03MB1782; BCL:0; PCL:0; RULEID:; SRVR:KL1PR03MB1782; x-forefront-prvs: 0812095267 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(199003)(13464003)(164054003)(189002)(377454003)(5004730100002)(102836003)(1220700001)(5003600100002)(189998001)(19580405001)(77096005)(76176999)(54356999)(97736004)(586003)(11100500001)(40100003)(87936001)(110136002)(6116002)(74316001)(5002640100001)(1096002)(101416001)(33656002)(81156007)(50986999)(76576001)(10400500002)(4326007)(2950100001)(122556002)(3846002)(5008740100001)(19580395003)(2900100001)(92566002)(86362001)(66066001)(106356001)(105586002)(5001960100002); DIR:OUT; SFP:1101; SCL:1; SRVR:KL1PR03MB1782; 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: 05 Jan 2016 06:21:20.1808 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 258ac4e4-146a-411e-9dc8-79a9e12fd6da X-MS-Exchange-Transport-CrossTenantHeadersStamped: KL1PR03MB1782 X-OrganizationHeadersPreserved: KL1PR03MB1782.apcprd03.prod.outlook.com X-CrossPremisesHeadersPromoted: BLR-HES-EDG04.wipro.com X-CrossPremisesHeadersFiltered: BLR-HES-EDG04.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: Tue, 05 Jan 2016 06:21:27 -0000 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=3D0x7f5b= 20ba2240 hw_ring=3D0x7f5b20ba2680 dma_addr=3D0xbf87a2680 PMD: eth_igb_tx_queue_setup(): To improve 1G driver performance, consider s= etting the TX WTHRESH value to 4, 8, or 16. PMD: eth_igb_tx_queue_setup(): sw_ring=3D0x7f5b20b910c0 hw_ring=3D0x7f5b20b= 92100 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=3D0x7f5b= 20b80a40 hw_ring=3D0x7f5b20b80e80 dma_addr=3D0xbf8780e80 PMD: eth_igb_tx_queue_setup(): To improve 1G driver performance, consider s= etting the TX WTHRESH value to 4, 8, or 16. PMD: eth_igb_tx_queue_setup(): sw_ring=3D0x7f5b20b6f8c0 hw_ring=3D0x7f5b20b= 70900 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 10000= 00 Traffic classes: period =3D 5000000, credits per period =3D [12207, 122= 07, 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 Please, tell me whether I am missing any other configuration. Thanks, Uday -----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 configurat= ion > multiple pfc can be configured in command line RX PORT - Specifies the packets receive port TX PORT - Specifies the packet= s 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 qo= s 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 p= ort 2 and transmit through port 3. In case of single qos sched instance, fo= llowing 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 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