DPDK patches and discussions
 help / color / mirror / Atom feed
From: Rajesh R <rajesh.arr@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] how to change binding of NIC ports to NUMA nodes
Date: Fri, 4 Sep 2015 00:29:21 -0400	[thread overview]
Message-ID: <CAAh6R8KMwkUenet8vjtDnoTfd89rJRkxNWVef_DxD+Co1Di2hQ@mail.gmail.com> (raw)

Hi,

I am trying an application based on dpdk on a 4- processor server i.e. 4
numa nodes.
The server is having with 4 NIC cards out of which 2 cards get binded to
numa node 0 and other 2 cards get binded to numa node 2 (as per the
/sys/pci/.../numa_node for each card)


How to evenly distribute the cards to all the numa nodes so that one card
each gets binded to one numa node?

Can we control the binding from dpdk, either pmd_ixgbe or igb_uio?


-- 
Regards

Rajesh R

             reply	other threads:[~2015-09-04  4:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  4:29 Rajesh R [this message]
2015-09-04  7:20 ` De Lara Guarch, Pablo
2015-09-04 17:29   ` Rajesh R

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=CAAh6R8KMwkUenet8vjtDnoTfd89rJRkxNWVef_DxD+Co1Di2hQ@mail.gmail.com \
    --to=rajesh.arr@gmail.com \
    --cc=dev@dpdk.org \
    /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).