DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Vlad Zolotarov <vladz@cloudius-systems.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DCA
Date: Tue, 21 Apr 2015 10:27:48 +0100	[thread overview]
Message-ID: <20150421092748.GB5360@bricha3-MOBL3> (raw)
In-Reply-To: <55360F9C.7070601@cloudius-systems.com>

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

  reply	other threads:[~2015-04-21  9:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 10:07 Vlad Zolotarov
2015-04-20 10:50 ` Bruce Richardson
2015-04-21  8:51   ` Vlad Zolotarov
2015-04-21  9:27     ` Bruce Richardson [this message]
2015-04-21  9:47       ` Vlad Zolotarov
2015-04-21 17:44       ` Matthew Hall
2015-04-22  9:10         ` Bruce Richardson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150421092748.GB5360@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=vladz@cloudius-systems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).