On 23/9/2021 9:11 AM, David Marchand wrote:
On Wed, Sep 22, 2021 at 2:29 PM David Hunt <david.h...@intel.com> wrote:
If the user requests to use an lcore above 128 using -l,
the eal will exit with "EAL: invalid core list 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 "-l 12-16,130,132" is used, we see the following
additional output on the command line:
EAL: lcore 132 >= RTE_MAX_LCORE (128)
EAL: lcore 133 >= 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@12,1@13,2@14,3@15,4@16,5@132,6@133
Signed-off-by: David Hunt <david.h...@intel.com>
Acked-by: Bruce Richardson <bruce.richard...@intel.com>
This series is there to help users, it should not break existing
working configurations.
I mentionned the "-l 0-3,0" case before.
This syntax is debatable, but it worked before (see comment below) and
this patch now refuses it.
Hi David,
Good point that the patch should not change behaviour. Will address,
along with your other comments.
Thanks,
Dave.
--snip--
