From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 120345A31 for ; Tue, 21 Apr 2015 11:27:51 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 21 Apr 2015 02:27:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,614,1422950400"; d="scan'208";a="683274920" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.220.106]) by orsmga001.jf.intel.com with SMTP; 21 Apr 2015 02:27:49 -0700 Received: by (sSMTP sendmail emulation); Tue, 21 Apr 2015 10:27:48 +0025 Date: Tue, 21 Apr 2015 10:27:48 +0100 From: Bruce Richardson To: Vlad Zolotarov Message-ID: <20150421092748.GB5360@bricha3-MOBL3> References: <5534CFFF.7000404@cloudius-systems.com> <20150420105020.GB9280@bricha3-MOBL3> <55360F9C.7070601@cloudius-systems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55360F9C.7070601@cloudius-systems.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] DCA X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2015 09:27:52 -0000 On Tue, Apr 21, 2015 at 11:51:40AM +0300, Vlad Zolotarov wrote: > > > On 04/20/15 13:50, Bruce Richardson wrote: > >On Mon, Apr 20, 2015 at 01:07:59PM +0300, Vlad Zolotarov wrote: > >>Hi, > >>I would like to ask if there is any reason why DPDK doesn't have support for > >>DCA feature? > >> > >>thanks, > >>vlad > >With modern platforms with DDIO the data written by the NIC automatically goes > >into the cache of the CPU without us needing to use DCA. > Thanks for a reply, Bruce. > One question though. According to DDIO documentation it only affects the > CPUs "local" relatively to the NIC. DCA, on the other hand may be configured > to work with any CPU. Modern platforms usually have a few NUMA nodes and > requirement of binding network handling threads only to CPUs "local" to the > NIC is very limiting. > > Could u, pls., comment on this? > > thanks in advance, > vlad > My main comment is that yes, you are correct. DDIO only works with the local socket, while DCA can be made to work with remote sockets. If you need to do polling on a device from a remote socket you may need to look at DCA. Can you perhaps comment on the use-case where you find this binding limiting? Modern platforms have multiple NUMA nodes, but they also generally have PCI slots connected to those multiple NUMA nodes also, so that you can have your NIC ports similarly NUMA partitionned? /Bruce