> > --- a/lib/eal/common/eal_common_memzone.c
> > +++ b/lib/eal/common/eal_common_memzone.c
> > +#define DEFAULT_MAX_MEMZONE 2560
>
> Maybe add "_COUNT" at the end to make clear it is not about the size of a
> memzone.
> We should add a comment here to explain the meaning of this default:
> used u
25/05/2023 00:25, Ophir Munk:
> --- a/config/rte_config.h
> +++ b/config/rte_config.h
> -#define RTE_MAX_MEMZONE 2560
Good to be able to remove this compilation-time configuration.
> --- a/lib/eal/common/eal_common_memzone.c
> +++ b/lib/eal/common/eal_common_memzone.c
> +#define DEFAULT_MAX_MEMZ
> -Original Message-
> Subject: Re: [PATCH v4] lib: set/get max memzone segments
>
> On 5/24/2023 11:25 PM, Ophir Munk wrote:
> > Currently, the max memzones count constat (RTE_MAX_MEMZONE) is used
> to
> > decide how many memzones a DPDK application
> -Original Message-
> From: David Marchand
> Sent: 26 May 2023 15:25
> To: Devendra Singh Rawat ; Alok Prasad
>
> Cc: dev@dpdk.org; Bruce Richardson ; Ophir Munk
> ; Matan Azrad
> ; Thomas Monjalon ; Lior Margalit
>
> Subject: [EXT] Re: [PATCH v4] lib
On Thu, May 25, 2023 at 12:26 AM Ophir Munk wrote:
>
> Currently, the max memzones count constat (RTE_MAX_MEMZONE) is used to
> decide how many memzones a DPDK application can have. This value could
> technically be changed by manually editing `rte_config.h` before
> compilation, but if DPDK is al
On 5/24/2023 11:25 PM, Ophir Munk wrote:
Currently, the max memzones count constat (RTE_MAX_MEMZONE) is used to
decide how many memzones a DPDK application can have. This value could
technically be changed by manually editing `rte_config.h` before
compilation, but if DPDK is already compiled, tha
6 matches
Mail list logo