Re: [RFC v3 1/6] eal: add static per-lcore memory allocation facility

2024-02-23 Thread Mattias Rönnblom
On 2024-02-22 10:22, Morten Brørup wrote: From: Mattias Rönnblom [mailto:mattias.ronnb...@ericsson.com] Sent: Tuesday, 20 February 2024 09.49 Introduce DPDK per-lcore id variables, or lcore variables for short. An lcore variable has one value for every current and future lcore id-equipped threa

RE: [RFC v3 1/6] eal: add static per-lcore memory allocation facility

2024-02-22 Thread Morten Brørup
> From: Mattias Rönnblom [mailto:mattias.ronnb...@ericsson.com] > Sent: Tuesday, 20 February 2024 09.49 > > Introduce DPDK per-lcore id variables, or lcore variables for short. > > An lcore variable has one value for every current and future lcore > id-equipped thread. > > The primary use case

Re: [RFC v3 1/6] eal: add static per-lcore memory allocation facility

2024-02-21 Thread Mattias Rönnblom
On 2024-02-21 10:43, Jerin Jacob wrote: On Tue, Feb 20, 2024 at 2:35 PM Mattias Rönnblom wrote: Introduce DPDK per-lcore id variables, or lcore variables for short. An lcore variable has one value for every current and future lcore id-equipped thread. The primary use case is for statically

RE: [RFC v3 1/6] eal: add static per-lcore memory allocation facility

2024-02-21 Thread Morten Brørup
> From: Jerin Jacob [mailto:jerinjac...@gmail.com] > Sent: Wednesday, 21 February 2024 10.44 > > On Tue, Feb 20, 2024 at 2:35 PM Mattias Rönnblom > wrote: > > > > Introduce DPDK per-lcore id variables, or lcore variables for short. > > > > An lcore variable has one value for every current and fut

Re: [RFC v3 1/6] eal: add static per-lcore memory allocation facility

2024-02-21 Thread Jerin Jacob
On Tue, Feb 20, 2024 at 2:35 PM Mattias Rönnblom wrote: > > Introduce DPDK per-lcore id variables, or lcore variables for short. > > An lcore variable has one value for every current and future lcore > id-equipped thread. > > The primary use case is for statically allocating > small chunks of oft

Re: [RFC v3 1/6] eal: add static per-lcore memory allocation facility

2024-02-20 Thread Mattias Rönnblom
On 2024-02-20 12:39, Bruce Richardson wrote: On Tue, Feb 20, 2024 at 11:47:14AM +0100, Mattias Rönnblom wrote: On 2024-02-20 10:11, Bruce Richardson wrote: On Tue, Feb 20, 2024 at 09:49:03AM +0100, Mattias Rönnblom wrote: Introduce DPDK per-lcore id variables, or lcore variables for short. An

RE: [RFC v3 1/6] eal: add static per-lcore memory allocation facility

2024-02-20 Thread Morten Brørup
> From: Bruce Richardson [mailto:bruce.richard...@intel.com] > Sent: Tuesday, 20 February 2024 12.39 > > On Tue, Feb 20, 2024 at 11:47:14AM +0100, Mattias Rönnblom wrote: > > On 2024-02-20 10:11, Bruce Richardson wrote: > > > On Tue, Feb 20, 2024 at 09:49:03AM +0100, Mattias Rönnblom wrote: > > >

Re: [RFC v3 1/6] eal: add static per-lcore memory allocation facility

2024-02-20 Thread Bruce Richardson
On Tue, Feb 20, 2024 at 11:47:14AM +0100, Mattias Rönnblom wrote: > On 2024-02-20 10:11, Bruce Richardson wrote: > > On Tue, Feb 20, 2024 at 09:49:03AM +0100, Mattias Rönnblom wrote: > > > Introduce DPDK per-lcore id variables, or lcore variables for short. > > > > > > An lcore variable has one va

Re: [RFC v3 1/6] eal: add static per-lcore memory allocation facility

2024-02-20 Thread Mattias Rönnblom
On 2024-02-20 10:11, Bruce Richardson wrote: On Tue, Feb 20, 2024 at 09:49:03AM +0100, Mattias Rönnblom wrote: Introduce DPDK per-lcore id variables, or lcore variables for short. An lcore variable has one value for every current and future lcore id-equipped thread. The primary use case is fo

Re: [RFC v3 1/6] eal: add static per-lcore memory allocation facility

2024-02-20 Thread Bruce Richardson
On Tue, Feb 20, 2024 at 09:49:03AM +0100, Mattias Rönnblom wrote: > Introduce DPDK per-lcore id variables, or lcore variables for short. > > An lcore variable has one value for every current and future lcore > id-equipped thread. > > The primary use case is for statically allocating > small chun