From: David Marchand <david.marchand@redhat.com>
To: David Hunt <david.hunt@intel.com>
Cc: dev <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v5 2/2] eal: add additional info if core mask too long
Date: Tue, 2 Nov 2021 18:45:48 +0100 [thread overview]
Message-ID: <CAJFAV8wkkTO0Mu2MdGD0yPj2hs+HMaZM8pO-yuGxv-X7KAASzA@mail.gmail.com> (raw)
In-Reply-To: <20210923110213.21350-2-david.hunt@intel.com>
On Thu, Sep 23, 2021 at 1:03 PM David Hunt <david.hunt@intel.com> wrote:
>
> If the user requests to use an lcore above 128 using -c,
> the eal will exit with "EAL: invalid coremask syntax" and
> very little else useful information.
>
> This patch adds some extra information suggesting to use --lcores
> so that physical cores above RTE_MAX_LCORE (default 128) can be
> used. This is achieved by using the --lcores option by mapping
> the logical cores in the application to physical cores.
>
> For example, if "-c 0x300000000000000000000000000000000" is
> used, we see the following additional output on the command line:
>
> EAL: lcore 128 >= RTE_MAX_LCORE (128)
> EAL: lcore 129 >= RTE_MAX_LCORE (128)
> EAL: to use high physical core ids , please use --lcores to
> map them to lcore ids below RTE_MAX_LCORE,
> EAL: e.g. --lcores 0@128,1@129
>
> Signed-off-by: David Hunt <david.hunt@intel.com>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> changes in v3
> * added this patch to the set. Addresses the changes for
> the -c option.
> changes in v4
> * fixed buffer overrun in populating lcore array.
> * switched from strlcpy to strdup due to a clang error.
> changes in v5
> * replaced strdup and frees with a const char *, as we
> just need to keep track of original pointer location.
> * reverted err: usage to return -1, as no free() needed.
> * other minod code cleanups.
> ---
> ---
> lib/eal/common/eal_common_options.c | 47 ++++++++++++++++++++++++-----
> 1 file changed, 40 insertions(+), 7 deletions(-)
>
> diff --git a/lib/eal/common/eal_common_options.c b/lib/eal/common/eal_common_options.c
> index 72735e0b09..7f715e4c15 100644
> --- a/lib/eal/common/eal_common_options.c
> +++ b/lib/eal/common/eal_common_options.c
> @@ -750,10 +750,12 @@ check_core_list(int *lcores, unsigned int count)
> static int
> eal_parse_coremask(const char *coremask, int *cores)
> {
> - unsigned count = 0;
> + unsigned int count = 0;
> int i, j, idx;
> int val;
> char c;
> + int lcores[RTE_MAX_LCORE];
> + const char *coremask_orig = coremask;
>
> for (idx = 0; idx < RTE_MAX_LCORE; idx++)
> cores[idx] = -1;
> @@ -770,29 +772,60 @@ eal_parse_coremask(const char *coremask, int *cores)
> i = strlen(coremask);
> while ((i > 0) && isblank(coremask[i - 1]))
> i--;
> - if (i == 0)
> + if (i == 0) {
> + RTE_LOG(ERR, EAL, "No lcores in coremask: [%s]\n",
> + coremask_orig);
> return -1;
> + }
>
> - for (i = i - 1; i >= 0 && idx < RTE_MAX_LCORE; i--) {
> + for (i = i - 1; i >= 0; i--) {
This loop exit condition changes here: this ensures that, once we
leave the loop, i == -1.
As a consequence... (see below)
> c = coremask[i];
> if (isxdigit(c) == 0) {
> /* invalid characters */
> + RTE_LOG(ERR, EAL, "invalid characters in coremask: [%s]\n",
> + coremask_orig);
> return -1;
> }
> val = xdigit2val(c);
> - for (j = 0; j < BITS_PER_HEX && idx < RTE_MAX_LCORE; j++, idx++)
> + for (j = 0; j < BITS_PER_HEX; j++, idx++)
> {
> if ((1 << j) & val) {
> - cores[idx] = count;
> + if (count >= RTE_MAX_LCORE) {
> + RTE_LOG(ERR, EAL, "Too many lcores provided. Cannot exceed %d\n",
> + RTE_MAX_LCORE);
> + return -1;
> + }
> + lcores[count] = idx;
> count++;
> }
> }
> }
... this loop below is dead code.
> for (; i >= 0; i--)
> - if (coremask[i] != '0')
> + if (coremask[i] != '0') {
> + RTE_LOG(ERR, EAL, "invalid characters in coremask: [%s]\n",
> + coremask_orig);
Nit: capital letter.
> return -1;
> - if (count == 0)
> + }
> + if (count == 0) {
> + RTE_LOG(ERR, EAL, "No lcores in coremask: [%s]\n",
> + coremask_orig);
> + return -1;
> + }
> +
> + if (check_core_list(lcores, count))
> return -1;
> +
> + /*
> + * Now that we've gto a list of cores no longer than
Same typo I commented on patch 1 for v4.
> + * RTE_MAX_LCORE, and no lcore in that list is greater
> + * than RTE_MAX_LCORE, populate the cores
> + * array and return.
> + */
> + do {
> + count--;
> + cores[lcores[count]] = count;
> + } while (count != 0);
> +
> return 0;
> }
>
> --
> 2.17.1
>
--
David Marchand
next prev parent reply other threads:[~2021-11-02 17:46 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 13:45 [dpdk-dev] build: Increase the default value of RTE_MAX_LCORE David Hunt
2021-09-09 13:45 ` [dpdk-dev] [PATCH v1 1/6] build: increase default of max lcores to 512 David Hunt
2021-09-09 14:37 ` Bruce Richardson
2021-09-10 6:51 ` David Marchand
2021-09-10 7:54 ` Bruce Richardson
2021-09-10 8:06 ` David Marchand
2021-09-10 8:24 ` Thomas Monjalon
2021-09-14 9:34 ` David Hunt
2021-09-14 10:00 ` David Marchand
2021-09-14 11:07 ` David Hunt
2021-09-14 11:29 ` David Marchand
2021-09-15 12:13 ` David Hunt
2021-11-17 15:55 ` Morten Brørup
2021-11-17 19:01 ` David Hunt
2021-09-15 12:11 ` [dpdk-dev] [PATCH v2] eal: add additional info if lcore exceeds max cores David Hunt
2021-09-16 12:34 ` David Marchand
2021-09-20 9:30 ` David Hunt
2021-09-21 11:50 ` [dpdk-dev] [PATCH v3 1/2] eal: add additional info if core list too long David Hunt
2021-09-21 11:50 ` [dpdk-dev] [PATCH v3 2/2] eal: add additional info if core mask " David Hunt
2021-09-21 12:00 ` Bruce Richardson
2021-09-21 11:57 ` [dpdk-dev] [PATCH v3 1/2] eal: add additional info if core list " Bruce Richardson
2021-09-21 12:04 ` David Hunt
2021-09-21 13:16 ` David Hunt
2021-09-21 13:20 ` Bruce Richardson
2021-09-21 13:51 ` David Marchand
2021-09-21 15:10 ` David Hunt
2021-09-22 12:29 ` [dpdk-dev] [PATCH v4 " David Hunt
2021-09-22 12:29 ` [dpdk-dev] [PATCH v4 2/2] eal: add additional info if core mask " David Hunt
2021-09-23 8:12 ` David Marchand
2021-09-23 10:21 ` David Hunt
2021-09-23 8:11 ` [dpdk-dev] [PATCH v4 1/2] eal: add additional info if core list " David Marchand
2021-09-23 9:47 ` David Hunt
2021-09-23 11:02 ` [dpdk-dev] [PATCH v5 " David Hunt
2021-09-23 11:02 ` [dpdk-dev] [PATCH v5 2/2] eal: add additional info if core mask " David Hunt
2021-11-02 17:45 ` David Marchand [this message]
2021-11-03 10:27 ` David Hunt
2021-11-03 10:29 ` David Marchand
2021-11-03 13:30 ` David Hunt
2021-11-03 14:32 ` [dpdk-dev] [PATCH v6 1/2] eal: add additional info if core list " David Hunt
2021-11-03 14:32 ` [dpdk-dev] [PATCH v6 2/2] eal: add additional info if core mask " David Hunt
2021-11-05 10:50 ` David Marchand
2021-09-09 13:45 ` [dpdk-dev] [PATCH v1 2/6] lib/power: reduce memory footprint of acpi lib David Hunt
2021-09-09 13:45 ` [dpdk-dev] [PATCH v1 3/6] lib/power: reduce memory footprint of pstate lib David Hunt
2021-09-09 13:45 ` [dpdk-dev] [PATCH v1 4/6] lib/power: reduce memory footprint of cppc lib David Hunt
2021-09-09 13:45 ` [dpdk-dev] [PATCH v1 5/6] lib/power: reduce memory footprint of channels David Hunt
2021-09-09 13:45 ` [dpdk-dev] [PATCH v1 6/6] lib/power: switch empty poll to max cores config David Hunt
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=CAJFAV8wkkTO0Mu2MdGD0yPj2hs+HMaZM8pO-yuGxv-X7KAASzA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).