[dpdk-dev] [PATCH v3 1/2] eal: add additional info if core list too long

Bruce Richardson bruce.richardson at intel.com
Tue Sep 21 13:57:36 CEST 2021


On Tue, Sep 21, 2021 at 12:50:14PM +0100, David Hunt 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.
> 
> There is no change in functionalty, just additional messages
> suggesting how the --lcores option might be used for the supplied
> list of lcores. For example, if "-l 12-16,130,132" is used, we
> see the following additional output on the command line:
> 
> EAL: Error = One of the 7 cores provided exceeds RTE_MAX_LCORE (128)
> EAL: Please use --lcores instead, e.g.

Minor suggestion: it would be good to clarify how to use lcores and what is
happening here in the example. Something like: "Please use --lcores
instead, to map lower lcore ids onto higher-numbered cores", could help the
user understand better what is happening.

>      --lcores 0 at 12,1 at 13,2 at 14,3 at 15,4 at 16,5 at 130,6 at 132
> 
> Signed-off-by: David Hunt <david.hunt at intel.com>

With some more info to help the user:

Acked-by: Bruce Richardson <bruce.richardson at intel.com>


More information about the dev mailing list