From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Wu, Jingjing" Subject: Re: net/i40e: latency issue due fix interrupt throttling setting in PF Date: Tue, 28 Nov 2017 12:50:01 +0000 Message-ID: <9BB6961774997848B5B42BEC655768F810EC8AC3@SHSMSX103.ccr.corp.intel.com> References: <3f57eb6982af4bb9aae69bce67233d89@XCH-RTP-017.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable To: "Hanoch Haim (hhaim)" , "dev@dpdk.org" Return-path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 3C92E1D90 for ; Tue, 28 Nov 2017 13:50:05 +0100 (CET) In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, Hanoch Are you talking about i40 VF's latency? And you are using DPDK PF as host d= river? In this case, we are setting the Interrupt Throttling (ITR) to be maximum. = That is to say, if the packet rate is very slow , the receive descriptor is= written back when ITR timeout, otherwise it is written back when cache li= ne is full (4 descriptors/packets). I think that's why you saw the latency = is varying. If we change the ITR to minor, then huge number of interrupts will coming t= o core which impact performance. Thanks Jingjing From: Hanoch Haim (hhaim) [mailto:hhaim@cisco.com] Sent: Friday, November 24, 2017 7:25 PM To: dev@dpdk.org Cc: Wu, Jingjing Subject: RE: [dpdk-dev] net/i40e: latency issue due fix interrupt throttlin= g setting in PF Re-sending Hanoh From: Hanoch Haim (hhaim) Sent: Monday, November 20, 2017 5:19 PM To: dev@dpdk.org Cc: Wu, Jingjing (jingjing.wu@intel.com); Han= och Haim (hhaim) Subject: [dpdk-dev] net/i40e: latency issue due fix interrupt throttling se= tting in PF Hi All, While integrating dpdk17.11 into TRex latest code a new latency issue is ob= served (i40e is very sensitive because it has very good resolution due to = Qos configuration). git bitsec found the following commit. With this commit we observe high spikes of Rx latency (~40usec) vs (~8usec)= . Any idea why? I can send how to reproduce this, it is very simple. cfd662d22e7bddb4ba41dbd1384f8497f38c2b4e is the first bad commit commit cfd662d22e7bddb4ba41dbd1384f8497f38c2b4e Author: Jingjing Wu > Date: Thu Aug 24 09:57:51 2017 +0800 net/i40e: fix interrupt throttling setting in PF As no matter the PF host driver is DPDK or other kernel drivers, they are sharing the same virtchnnl interfaces to communicate to VFs. To follow the generic interface, DPDK PF need to set Interrupt Throttling (ITR) index according to the rxitr_idx from virtchnnl instead of ITR_NONE. Fixes: 6d59e4ea74a6 ("net/i40e: change version number to support Linux = VF") Cc: stable@dpdk.org Signed-off-by: Jingjing Wu > Thanks, Hanoh