From: "Martin Drašar" <drasar@ics.muni.cz>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Running multiple threads on a single core
Date: Tue, 22 Sep 2015 10:37:08 +0200 [thread overview]
Message-ID: <56011334.2050603@ics.muni.cz> (raw)
In-Reply-To: <560015C5.6080101@ics.muni.cz>
Dne 21.9.2015 v 16:35 Martin Drašar napsal(a):
> Hi,
>
> I have a hard time understanding the configuration of multiple pthreads
> in eal initialization.
>
> Let's say I have a 4 lcore machine (2 phys. cores with HT) and I want to
> run 7 threads on it.
>
> I thought that these options would help me:
>
> -c 0xf -l 0-6 --lcores='0,(1,3)@2,(2,4)@3,(5,6)@1'
>
> But all I am getting is "EAL: invalid parameter for --lcores".
>
> So my question is - how can I tell EAL to start 7 threads, pin them to
> given CPUs and made them accessible as lcores for issuing
> rte_eal_remote_launch?
>
> Thanks in advance,
> Martin
>
Ok, figured it out... I am feeding the options by manually constructing
the argv and the option must not be passed with quotes.
So:
argv[x] = "--lcores=0,(1,3)@2,(2,4)@3,(5,6)@1"
Martin
prev parent reply other threads:[~2015-09-22 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 14:35 Martin Drašar
2015-09-22 8:37 ` Martin Drašar [this message]
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=56011334.2050603@ics.muni.cz \
--to=drasar@ics.muni.cz \
--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).