From: Simon Kuenzer <simon.kuenzer-kcmmt4fgdiuHXe+LvDLADg@public.gmane.org>
To: Hiroshi Shimamoto
<h-shimamoto-ehU+Cx/zZe18UrSeD/g0lQ@public.gmane.org>,
Thomas Monjalon
<thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: [PATCH] eal/linuxapp: Add parameter to specify master lcore id
Date: Wed, 23 Jul 2014 14:10:31 +0200 [thread overview]
Message-ID: <53CFA637.1090706@neclab.eu> (raw)
In-Reply-To: <7F861DC0615E0C47A872E6F3C5FCDDBD011625D2-ZmjkEB1lVlLt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
Hi all,
the only issue I could imagine is that current DPDK applications are
utilizing the implicit assumption that the master lcore is always set to
the first available lcore. I would consider this as a "bug" in the
application because it sets up its worker threads not "properly".
However, as far I could check it, the DPDK framework seems to cope with
it correctly.
It would be nice if somebody else could confirm my statement.
Thanks,
Simon
On 23.07.2014 10:53, Hiroshi Shimamoto wrote:
> Hi,
>
>> Subject: Re: [dpdk-dev] [PATCH] eal/linuxapp: Add parameter to specify master lcore id
>>
>> Hi Hiroshi,
>>
>> 2014-07-22 23:40, Hiroshi Shimamoto:
>>> does anyone have interest in this functionality?
>>>
>>> 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.
>>
>> Thank you for showing your interest.
>> Does it mean you carefully reviewed this patch? In this case, I'd appreciate
>> a note "Reviewed-by:".
>
> Not yet deeply, wait a bit, we're testing this patch in our application.
> Will report if it works fine.
>
> By the way, we should add the same code into the BSD code, right?
>
> thanks,
> Hiroshi
>
>>
>> Thanks
>> --
>> Thomas
next prev parent reply other threads:[~2014-07-23 12:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 8:28 [PATCH] eal/linuxapp: Add parameter to specify master lcore id Simon Kuenzer
[not found] ` <1404808110-16314-1-git-send-email-simon.kuenzer-kcmmt4fgdiuHXe+LvDLADg@public.gmane.org>
2014-07-08 9:42 ` Simon Kuenzer
[not found] ` <53BBBCFC.1070907-kcmmt4fgdiuHXe+LvDLADg@public.gmane.org>
2014-07-21 16:21 ` Simon Kuenzer
[not found] ` <53CD3E26.1060708-kcmmt4fgdiuHXe+LvDLADg@public.gmane.org>
2014-07-22 23:40 ` Hiroshi Shimamoto
[not found] ` <7F861DC0615E0C47A872E6F3C5FCDDBD01161242-ZmjkEB1lVlLt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
2014-07-23 7:50 ` Thomas Monjalon
2014-07-23 8:53 ` Hiroshi Shimamoto
[not found] ` <7F861DC0615E0C47A872E6F3C5FCDDBD011625D2-ZmjkEB1lVlLt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
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 [this message]
[not found] ` <53CFA637.1090706-kcmmt4fgdiuHXe+LvDLADg@public.gmane.org>
2014-11-03 17:02 ` Aaron Campbell
[not found] ` <CDC4C356-008C-4099-A6BB-16D931CBBF52-rd7evPjynkNeoWH0uzbU5w@public.gmane.org>
2014-11-03 22:29 ` Thomas Monjalon
2014-07-23 8:03 ` Gray, Mark D
2014-11-03 17:02 ` Aaron Campbell
[not found] ` <582DA5F6-0A84-4FDD-8DC6-D8E5C6B1652A-rd7evPjynkNeoWH0uzbU5w@public.gmane.org>
2014-11-04 19:00 ` Thomas Monjalon
2014-11-05 15:34 ` Aaron Campbell
2014-11-04 21:40 ` [PATCH v2] eal: add option --master-lcore Thomas Monjalon
[not found] ` <1415137233-6364-1-git-send-email-thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-11-05 11:54 ` Ananyev, Konstantin
[not found] ` <2601191342CEEE43887BDE71AB977258213A2877-kPTMFJFq+rEu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
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=53CFA637.1090706@neclab.eu \
--to=simon.kuenzer-kcmmt4fgdiuhxe+lvdladg@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=h-shimamoto-ehU+Cx/zZe18UrSeD/g0lQ@public.gmane.org \
--cc=thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.