Re: [PATCH] eal: have unregistered non-EAL threads use dedicated PRNG

On Mon, Dec 5, 2022 at 11:08 AM Mattias Rönnblom wrote: > > Prior to this change, unregistered non-EAL threads shared a PRNG > instance with the main lcore. The main lcore may well be used for fast > path processing, potentially making rte_rand() calls in the > process. It should not need to synch

Re: [PATCH] eal: have unregistered non-EAL threads use dedicated PRNG

On 2022-12-05 11:58, Morten Brørup wrote: >> From: Mattias Rönnblom [mailto:mattias.ronnb...@ericsson.com] >> Sent: Monday, 5 December 2022 11.04 >> >> Prior to this change, unregistered non-EAL threads shared a PRNG >> instance with the main lcore. The main lcore may well be used for fast >> path

RE: [PATCH] eal: have unregistered non-EAL threads use dedicated PRNG

> From: Mattias Rönnblom [mailto:mattias.ronnb...@ericsson.com] > Sent: Monday, 5 December 2022 11.04 > > Prior to this change, unregistered non-EAL threads shared a PRNG > instance with the main lcore. The main lcore may well be used for fast > path processing, potentially making rte_rand() calls

[PATCH] eal: have unregistered non-EAL threads use dedicated PRNG

Prior to this change, unregistered non-EAL threads shared a PRNG instance with the main lcore. The main lcore may well be used for fast path processing, potentially making rte_rand() calls in the process. It should not need to synchronize with control threads. With this change, all unregistered no