From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by dpdk.org (Postfix) with ESMTP id 8FF365921 for ; Wed, 17 Aug 2016 14:07:04 +0200 (CEST) Received: from 172.24.1.136 (EHLO nkgeml412-hub.china.huawei.com) ([172.24.1.136]) by szxrg03-dlp.huawei.com (MOS 4.4.3-GA FastPath queued) with ESMTP id CGK47705; Wed, 17 Aug 2016 20:07:01 +0800 (CST) Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Wed, 17 Aug 2016 20:06:51 +0800 From: Caianning To: "users@dpdk.org" CC: Houzhipeng , Houyuzhu Thread-Topic: Does any thing wrong with the DPDK sample l2fwd-jobstats Thread-Index: AdH4fUo7yIoYqy4KS5GLBeqlL9BDqg== Date: Wed, 17 Aug 2016 12:06:50 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.111.146.139] MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.57B45366.0020, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 8e622e5c29819777a232055441fd013e Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Does any thing wrong with the DPDK sample l2fwd-jobstats X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2016 12:07:06 -0000 Hi, I noticed that when the pktgen(version 3.0.09) port 1 rx rate drop = to half of normal when l2fwd-jobstat shows Port statistics. (while l2fwd dr= opped packet is 0). And port 0 kept same as normal. DPDK version 16.07.0 My cmd line as following: Pktgen: pktgen -c 0x1ff -n 3 -- -P -m "[1-2:3-4].0,[5-6:7-8].1" with port 0 and port 1 started lwfwd-jobstats: l2fwd-jobstats -c 580000000 -- -p 3 but the l2fwd does not. Maybe some other processes disturbed the f= orwarding processing(alarm trig task re-schedule?), and Shall these cores b= e isolated? Thanks.