> -----Original Message----- > From: David Marchand <david.march...@redhat.com> > Sent: 26 May 2023 15:25 > To: Devendra Singh Rawat <dsinghra...@marvell.com>; Alok Prasad > <pa...@marvell.com> > Cc: dev@dpdk.org; Bruce Richardson <bruce.richard...@intel.com>; Ophir Munk > <ophi...@nvidia.com>; Matan Azrad > <ma...@nvidia.com>; Thomas Monjalon <tho...@monjalon.net>; Lior Margalit > <lmarga...@nvidia.com> > Subject: [EXT] Re: [PATCH v4] lib: set/get max memzone segments > > External Email > > ---------------------------------------------------------------------- > On Thu, May 25, 2023 at 12:26 AM Ophir Munk <ophi...@nvidia.com> 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, that option is not useful. > > There are certain use cases that would benefit from making this value > > configurable. > > > > This commit addresses the issue by adding a new API to set the max > > number of memzones before EAL initialization (while using the old > > constant as default value), as well as an API to get current maximum > > number of memzones. > > > > Signed-off-by: Ophir Munk <ophi...@nvidia.com> > > Acked-by: Morten Brørup <m...@smartsharesystems.com> > > qede maintainers, can you double check the change on your driver please? > Thanks. > > > -- > David Marchand
Acked-by: Alok Prasad <pa...@marvell.com>
