From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Damjan Marion (damarion)" Subject: rte_mbuf.next in 2nd cacheline Date: Wed, 10 Jun 2015 21:47:52 +0000 Message-ID: <87110795-201A-4A1E-A4CC-A778AA7C8218@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable To: "dev@dpdk.org" Return-path: Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by dpdk.org (Postfix) with ESMTP id 16F946849 for ; Wed, 10 Jun 2015 23:47:53 +0200 (CEST) Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t5ALlrta012849 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 10 Jun 2015 21:47:53 GMT Content-Language: en-US Content-ID: <4AB1C783E65199408E3356F7CE0D7E3E@emea.cisco.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" Hi, We noticed 7% performance improvement by simply moving rte_mbuf.next field = to the 1st cache line. Currently, it falls under /* second cache line - fields only used in slow p= ath or on TX */ but it is actually used at several places in rx fast path. (e.g.: i40e_rx_a= lloc_bufs() is setting that field to NULL). Is there anything we can do here (stop using next field, or move it to 1st = cache line)? Thanks, Damjan