From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v6] examples/l3fwd: em path performance fix Date: Mon, 21 Mar 2016 12:57:16 +0100 Message-ID: <4974706.HRff2DSHxK@xps13> References: <1458294767-5996-1-git-send-email-tomaszx.kulasek@intel.com> <1458307906-4824-1-git-send-email-tomaszx.kulasek@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Tomasz Kulasek Return-path: Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id DDE422C3F for ; Mon, 21 Mar 2016 12:58:54 +0100 (CET) Received: by mail-wm0-f48.google.com with SMTP id r129so47172791wmr.1 for ; Mon, 21 Mar 2016 04:58:54 -0700 (PDT) In-Reply-To: <1458307906-4824-1-git-send-email-tomaszx.kulasek@intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-03-18 14:31, Tomasz Kulasek: > It seems that for the most use cases, previous hash_multi_lookup provides > better performance, and more, sequential lookup can cause significant > performance drop. > > This patch sets previously optional hash_multi_lookup method as default. > It also provides some minor optimizations such as queue drain only on used > tx ports. Applied, thanks