All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] eal: fix recording of detected/enabled logical cores
Date: Fri, 26 Jul 2013 15:34:32 +0200	[thread overview]
Message-ID: <201307261534.32927.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <1374839749-28143-1-git-send-email-thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>

26/07/2013 13:55, Thomas Monjalon :
> From: Ivan Boule <ivan.boule-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
> 
> 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-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>

acked and pushed

-- 
Thomas

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 11:55 [PATCH] eal: fix recording of detected/enabled logical cores Thomas Monjalon
     [not found] ` <1374839749-28143-1-git-send-email-thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-07-26 12:13   ` Adrien Mazarguil
2013-07-26 13:34   ` Thomas Monjalon [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=201307261534.32927.thomas.monjalon@6wind.com \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@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.