From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: VMXNET3 on vmware, ping delay Date: Thu, 25 Jun 2015 15:36:09 -0700 Message-ID: <20150625223608.GA1890@mhcomputing.net> References: <792CF0A6B0883C45AF8C719B2ECA946E42B2430F@DEMUMBX003.nsn-intra.net> <20150625151834.GA29296@mhcomputing.net> <792CF0A6B0883C45AF8C719B2ECA946E42B24BD9@DEMUMBX003.nsn-intra.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev@dpdk.org" To: "Vass, Sandor (Nokia - HU/Budapest)" Return-path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 06FC7C742 for ; Fri, 26 Jun 2015 00:38:48 +0200 (CEST) Content-Disposition: inline In-Reply-To: <792CF0A6B0883C45AF8C719B2ECA946E42B24BD9@DEMUMBX003.nsn-intra.net> 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" On Thu, Jun 25, 2015 at 09:13:59PM +0000, Vass, Sandor (Nokia - HU/Budapest) wrote: > Can anyone tell me the reason of this behavior? Using CPU 1 there are huge > latencies, using other CPUs everything work as expected... One possible guess what could be related. Normally DPDK uses "Core #0" as the "master lcore". That core's behavior is ever so slightly different from other cores. Matthew.