From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id 6563E5A13 for ; Tue, 21 Apr 2015 10:51:44 +0200 (CEST) Received: by wgso17 with SMTP id o17so206045201wgs.1 for ; Tue, 21 Apr 2015 01:51:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=IdZIMSS9XXhCresntz7qYxi9XGxxWaD8j9yqvtj0Auk=; b=PBe+aPlYEe6jreDuKRaC7LcYU+n/RohymmLFhVChEyhgk4LUUXYlBcq/vF2FCdpRNJ +j0oQ+lRNa1JXkOR416rf0u8YWEFg44RtYiyDtnc1svJlKa/I3djmWzlckq3/WygjL/L 0Y+wnCut8l/1/Sj8F1ZsKOUf8L8tNwi9Q97gPYEg9SGn+FdnSYqOVbwk78ihhL7XuDCA zBV2lwLz1P6678FgQmU7SCXsx7Rn4yaEaVzpxkbtGwZVyYLFtQkwGsmSuwI2FxH3xgHd Jm5Hd8BhJk9Zu/IOFQd2tFkdrs5PZ9+W7wrx3vUxXRlCQcu0Y7dfBQmQYsr5x1RNkqgl aNOw== X-Gm-Message-State: ALoCoQmm+uCKZu1tgcpVMTpPVtWZu6wZ55YS+KMutuP8YmSptAEkuPo6fXfXabFcAY7e3VnPsnsn X-Received: by 10.194.177.132 with SMTP id cq4mr37273673wjc.99.1429606302484; Tue, 21 Apr 2015 01:51:42 -0700 (PDT) Received: from [10.0.0.166] ([212.143.139.214]) by mx.google.com with ESMTPSA id di9sm18692320wib.16.2015.04.21.01.51.41 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Apr 2015 01:51:42 -0700 (PDT) Message-ID: <55360F9C.7070601@cloudius-systems.com> Date: Tue, 21 Apr 2015 11:51:40 +0300 From: Vlad Zolotarov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Bruce Richardson References: <5534CFFF.7000404@cloudius-systems.com> <20150420105020.GB9280@bricha3-MOBL3> In-Reply-To: <20150420105020.GB9280@bricha3-MOBL3> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 08:51:44 -0000 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 > > /Bruce