DPDK patches and discussions
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: fix recording of detected/enabled logical cores
Date: Fri, 26 Jul 2013 14:13:16 +0200	[thread overview]
Message-ID: <20130726121316.GL7849@6wind.com> (raw)
In-Reply-To: <1374839749-28143-1-git-send-email-thomas.monjalon@6wind.com>

On Fri, Jul 26, 2013 at 01:55:49PM +0200, Thomas Monjalon wrote:
> From: Ivan Boule <ivan.boule@6wind.com>
> 
> 1) In the EAL initialization phase, invoke the function rte_eal_cpu_init
>    to detect the set of running cores (and enable them by default) before
>    processing the [enabled] core mask option that is performed during the
>    parsing of EAL arguments.
> 
> 2) In the function rte_eal_cpu_init():
>    - to parse the set of all running logical cores on the machine, do not
>      use the RTE_LCORE_FOREACH macro that considers the set of already
>      detected cores...
>      Instead, use a standard loop based on the RTE_MAX_LCORE constant.
>    - explicitely set to ROLE_RTE the role of each detected logical core
>      that is recorded in the EAL configuration, as all running cores are
>      enabled by default.
> 
> 3) In the function eal_parse_coremask(), update the "lcore_count" field
>    of the EAL configuration with the effective number of logical cores
>    that are set in the mask of enabled logical cores.
> 
> Signed-off-by: Ivan Boule <ivan.boule@6wind.com>
> ---
>  lib/librte_eal/linuxapp/eal/eal.c       |    8 +++++---
>  lib/librte_eal/linuxapp/eal/eal_lcore.c |   12 ++++++++----
>  2 files changed, 13 insertions(+), 7 deletions(-)

Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2013-07-26 12:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 11:55 Thomas Monjalon
2013-07-26 12:13 ` Adrien Mazarguil [this message]
2013-07-26 13:34 ` Thomas Monjalon

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=20130726121316.GL7849@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    /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).