[PATCH v14 0/7] Lcore variables
Stephen Hemminger
stephen at networkplumber.org
Wed Oct 16 16:58:10 CEST 2024
On Wed, 16 Oct 2024 15:19:09 +0200
Mattias Rönnblom <mattias.ronnblom at ericsson.com> wrote:
> This patch set introduces a new API <rte_lcore_var.h> for static
> per-lcore id data allocation.
>
> Please refer to the <rte_lcore_var.h> API documentation for both a
> rationale for this new API, and a comparison to the alternatives
> available.
>
> The question on how to best allocate static per-lcore memory has been
> up several times on the dev mailing list, for example in the thread on
> "random: use per lcore state" RFC by Stephen Hemminger.
>
> Lcore variables are surely not the answer to all your per-lcore-data
> needs, since it only allows for more-or-less static allocation. In the
> author's opinion, it does however provide a reasonably simple and
> clean and seemingly very much performant solution to a real problem.
>
> Mattias Rönnblom (7):
> eal: add static per-lcore memory allocation facility
> eal: add lcore variable functional tests
> eal: add lcore variable performance test
> random: keep PRNG state in lcore variable
> power: keep per-lcore state in lcore variable
> service: keep per-lcore state in lcore variable
> eal: keep per-lcore power intrinsics state in lcore variable
Still too wordy, would you mind if I have a try and summarizing and
running the text through an editor tool?
More information about the dev
mailing list