From: Stephen Hemminger <stephen@networkplumber.org>
To: Cliff Burdick <shaklee3@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Coremask
Date: Wed, 13 Apr 2016 11:10:13 -0700 [thread overview]
Message-ID: <20160413111013.2d56cb28@xeon-e3> (raw)
In-Reply-To: <CA+Gp1nZC3wR1p5NQh2zcB1doaxNvSfhijFLo3rh5-iWOkT1YqQ@mail.gmail.com>
On Wed, 13 Apr 2016 09:42:29 -0700
Cliff Burdick <shaklee3@gmail.com> wrote:
> I don't see the answer to this in the documentation, so I'll try here. Why
> function does the coremask that's required in rte_eal_init() actually do
> other than tell the API what cores you're using? In other words, can't I
> just set the core mask to all of the cores in my system, and selectively
> use the ones I want? Is there a downside to that? What if the particular
> thread running on an lcore isn't doing any DPDK functions?
The coremask is used to determine which CPU's are setup and a per-cpu
thread is started by the launch operation.
You can tell EAL about as many CPU's as you want, either all or even
just one. If you use all CPU's, then in the launch it is possible to
have the thread function of unneeded CPU's return and go back to the launch idle loop.
next prev parent reply other threads:[~2016-04-13 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 16:42 Cliff Burdick
2016-04-13 18:10 ` Stephen Hemminger [this message]
2016-04-15 21:57 ` Cliff Burdick
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=20160413111013.2d56cb28@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=shaklee3@gmail.com \
--cc=users@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).