[PATCH] eal: fix core_index for non-EAL registered threads

David Marchand david.marchand at redhat.com
Thu Jun 11 12:13:21 CEST 2026


On Wed, 10 Jun 2026 at 15:46, Maxime Peim <maxime.peim at gmail.com> wrote:
>
> I am not sure it works either, if the lcore are manual set with a gap: `--lcores=0,7` (from `eal_parse_lcores`):
> - lcore 0 will get core_index = 0
> - lcore 7 will get core_index = 1
>
> When calling `rte_thread_register` we will hit lcore=1 as first not-assigned lcore and set core_index=1 as well.

Ah ah yes...

> It seems like a solution should be to have a bitmap of the currently used core_index stored in the global config.

Yes, it seems the right way to handle this.
We have a rte_bitmap API but it is probably simpler to go with a rte_bitset.


-- 
David Marchand



More information about the dev mailing list