From: "Gray, Mark D" <mark.d.gray@intel.com>
To: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
Simon Kuenzer <simon.kuenzer@neclab.eu>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal/linuxapp: Add parameter to specify master lcore id
Date: Wed, 23 Jul 2014 08:03:55 +0000 [thread overview]
Message-ID: <738D45BC1F695740A983F43CFE1B7EA92D6EFD32@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <7F861DC0615E0C47A872E6F3C5FCDDBD01161242@BPXM14GP.gisp.nec.co.jp>
> Hi all,
>
> does anyone have interest in this functionality?
Yes, I think this is useful for DPDK vSwitch.
>
> I think this is important and useful.
> Since we should care about core assignment to get high performance and the
> master lcore thread is special in DPDK, we will want to assign the master to
> the target core.
> For example, with hyperthreading I'd like to make a pair of packet processing
> threads into one physical core and separate the master thread which does
> some management.
>
> thanks,
> Hiroshi
>
next prev parent reply other threads:[~2014-07-23 8:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 8:28 Simon Kuenzer
2014-07-08 9:42 ` Simon Kuenzer
2014-07-21 16:21 ` Simon Kuenzer
2014-07-22 23:40 ` Hiroshi Shimamoto
2014-07-23 7:50 ` Thomas Monjalon
2014-07-23 8:53 ` Hiroshi Shimamoto
2014-07-23 9:04 ` Thomas Monjalon
2014-07-23 12:05 ` Simon Kuenzer
2014-08-04 2:48 ` Hiroshi Shimamoto
2014-07-23 12:10 ` Simon Kuenzer
2014-11-03 17:02 ` Aaron Campbell
2014-11-03 22:29 ` Thomas Monjalon
2014-07-23 8:03 ` Gray, Mark D [this message]
2014-11-03 17:02 ` Aaron Campbell
2014-11-04 19:00 ` Thomas Monjalon
2014-11-05 15:34 ` Aaron Campbell
2014-11-04 21:40 ` [dpdk-dev] [PATCH v2] eal: add option --master-lcore Thomas Monjalon
2014-11-05 11:54 ` Ananyev, Konstantin
2014-11-05 16:52 ` Thomas Monjalon
2014-11-05 15:34 ` Aaron Campbell
2014-11-05 23:43 ` Simon Kuenzer
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=738D45BC1F695740A983F43CFE1B7EA92D6EFD32@IRSMSX102.ger.corp.intel.com \
--to=mark.d.gray@intel.com \
--cc=dev@dpdk.org \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=simon.kuenzer@neclab.eu \
/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).