Re: [dpdk-dev] [PATCH] eal: fix out of bound access when no cpu is available

17/01/2019 18:17, David Marchand: > On Thu, Jan 17, 2019 at 5:34 PM Thomas Monjalon wrote: > > > 17/01/2019 14:12, David Marchand: > > > In the unlikely case when the dpdk application is started with no cpu > > > available in the [0, RTE_MAX_LCORE - 1] range, the master_lcore is > > > automatical

Re: [dpdk-dev] [PATCH] eal: fix out of bound access when no cpu is available

On Thu, Jan 17, 2019 at 5:34 PM Thomas Monjalon wrote: > 17/01/2019 14:12, David Marchand: > > In the unlikely case when the dpdk application is started with no cpu > > available in the [0, RTE_MAX_LCORE - 1] range, the master_lcore is > > automatically chosen as RTE_MAX_LCORE which triggers an o

Re: [dpdk-dev] [PATCH] eal: fix out of bound access when no cpu is available

17/01/2019 14:12, David Marchand: > In the unlikely case when the dpdk application is started with no cpu > available in the [0, RTE_MAX_LCORE - 1] range, the master_lcore is > automatically chosen as RTE_MAX_LCORE which triggers an out of bound > access. > > Either you have a crash then, or the i

[dpdk-dev] [PATCH] eal: fix out of bound access when no cpu is available

In the unlikely case when the dpdk application is started with no cpu available in the [0, RTE_MAX_LCORE - 1] range, the master_lcore is automatically chosen as RTE_MAX_LCORE which triggers an out of bound access. Either you have a crash then, or the initialisation fails later when trying to pin t