DPDK patches and discussions
 help / color / mirror / Atom feed
From: Muhammad Ali <Muhammad.Ali@xflowresearch.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Number of memory channels (EAL Options)
Date: Thu, 20 Jun 2013 16:20:35 +0500	[thread overview]
Message-ID: <CA+JBJ--bhvWOqpsosa=iw6ak=4vbeW7+nFAOis2YpcMa8ws7fw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 612 bytes --]

Hi everyone

I am running DPDK sample application compiled in Fedora 14 environment.

I have used following command to run the App

./<application> -c f -n 4

c= bitmask of cores to to be used.
and
n= number of memory channels

Now what does 'n' actually defines ?. Is this the number of DMA channels
between RAM (hugepages) and NIC. ? If not so then what it is ?

How does number of memory channels will effect the performance ?

BTW I am using hugepagesize=1G
and Number of Hugepages=4

My question might be very basic, but I am totally confused. Please help me
out here.

Thank you

Regards
-- 

Muhammad Ali

[-- Attachment #2: Type: text/html, Size: 1157 bytes --]

             reply	other threads:[~2013-06-20 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 11:20 Muhammad Ali [this message]
2013-06-20 15:43 ` Stephen Hemminger
2013-06-24  5:27   ` Muhammad Ali

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='CA+JBJ--bhvWOqpsosa=iw6ak=4vbeW7+nFAOis2YpcMa8ws7fw@mail.gmail.com' \
    --to=muhammad.ali@xflowresearch.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).