2024-05-05 03:25 (UTC+), Lombardo, Ed:
> Hi Dmitry,
> I tried your settings tonight and the application VIRT memory is now 7.9G and
> is in the ball park, you are amazing.
>
> #define RTE_MAX_MEMSEG_LISTS 2
> #define RTE_MAX_MEMSEG_PER_LIST 1024
> #define RTE_MAX_MEM_MB_PER_LIST 2048
> #defin
: Need help with reducing VIRT memory
External Email: This message originated outside of NETSCOUT. Do not click links
or open attachments unless you recognize the sender and know the content is
safe.
2024-05-03 23:54 (UTC+0300), Dmitry Kozlyuk:
> #define RTE_MAX_MEM_MB_PER_LIST 2024 // see i
> From: Lombardo, Ed [mailto:ed.lomba...@netscout.com]
> Sent: Friday, 3 May 2024 23.19
>
> Hi Dmitry,
> Thank you, I will give this a try.
Many arrays in DPDK are statically allocated at the build-time max array size,
so tweaking DPDK's build-time configuration parameters will reduce the memory
: dev@dpdk.org
Subject: Re: Need help with reducing VIRT memory
External Email: This message originated outside of NETSCOUT. Do not click links
or open attachments unless you recognize the sender and know the content is
safe.
2024-05-03 23:54 (UTC+0300), Dmitry Kozlyuk:
> #def
2024-05-03 23:54 (UTC+0300), Dmitry Kozlyuk:
> #define RTE_MAX_MEM_MB_PER_LIST 2024 // see item 4 below
Typo: 2048
2024-05-03 14:48 (UTC+), Lombardo, Ed:
> Hi Dmitry,
> I am not clear on the DPDK memory layout and how to tweak these #define
> values.
Given your statement:
> Currently we configure 2x1G hugepages and single socket.
I suggest the following:
#define RTE_MAX_MEMSEG_LISTS 2 // see i
the rte_config.h for MEMSEG would be a
viable path.
Regards,
Ed
-Original Message-
From: Morten Brørup
Sent: Friday, May 3, 2024 2:58 PM
To: Bruce Richardson ; Lombardo, Ed
Cc: Dmitry Kozlyuk ; dev@dpdk.org;
anatoly.bura...@intel.com
Subject: RE: Need help with reducing VIRT
> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> Sent: Friday, 3 May 2024 17.52
>
> On Fri, May 03, 2024 at 04:27:39PM +0100, Bruce Richardson wrote:
> > On Fri, May 03, 2024 at 02:48:12PM +, Lombardo, Ed wrote:
> > > Hi Dmitry,
> > > I am not clear on the DPDK memory layout and
On Fri, May 03, 2024 at 04:27:39PM +0100, Bruce Richardson wrote:
> On Fri, May 03, 2024 at 02:48:12PM +, Lombardo, Ed wrote:
> > Hi Dmitry,
> > I am not clear on the DPDK memory layout and how to tweak these #define
> > values.
> >
> > #define RTE_MAX_MEMSEG_PER_LIST 8192
> > #define RTE_M
On Fri, May 03, 2024 at 02:48:12PM +, Lombardo, Ed wrote:
> Hi Dmitry,
> I am not clear on the DPDK memory layout and how to tweak these #define
> values.
>
> #define RTE_MAX_MEMSEG_PER_LIST 8192
> #define RTE_MAX_MEM_MB_PER_LIST 32768
> #define RTE_MAX_MEMSEG_PER_TYPE 32768
> #define RTE_M
, May 2, 2024 4:04 PM
To: Lombardo, Ed
Cc: dev@dpdk.org
Subject: Re: Need help with reducing VIRT memory
External Email: This message originated outside of NETSCOUT. Do not click links
or open attachments unless you recognize the sender and know the content is
safe.
Hi Ed,
I presume it's
To: Lombardo, Ed
Cc: dev@dpdk.org
Subject: Re: Need help with reducing VIRT memory
External Email: This message originated outside of NETSCOUT. Do not click links
or open attachments unless you recognize the sender and know the content is
safe.
Hi Ed,
I presume it's a revival of this t
Hi Ed,
I presume it's a revival of this thread:
http://inbox.dpdk.org/users/ch3pr01mb8470c9675763e14954d6e3b88f...@ch3pr01mb8470.prod.exchangelabs.com/
2024-05-02 19:05 (UTC+), Lombardo, Ed:
[...]
> My situation is as follows:
> We were on DPDK 17.11.6 and upgraded to DPDK22.11.2 to
13 matches
Mail list logo
