On Thu, Jan 30, 2020 at 11:48 AM siddarth rai wrote:
> I did some further experiments and found out that version 18.02.2 doesn't
> have the problem, but the 18.05.1 release has it.
>
> Would really appreciate if someone can help, if there is a patch to get over
> this issue in the DPDK code ?
>
On 11-Feb-20 8:11 AM, David Marchand wrote:
Hello Anatoly,
On Tue, Feb 4, 2020 at 11:23 AM Burakov, Anatoly
wrote:
On 30-Jan-20 8:51 AM, David Marchand wrote:
On Thu, Jan 30, 2020 at 8:48 AM siddarth rai wrote:
I have been using DPDK 19.08 and I notice the process VSZ is huge.
I tried run
Hello Anatoly,
On Tue, Feb 4, 2020 at 11:23 AM Burakov, Anatoly
wrote:
>
> On 30-Jan-20 8:51 AM, David Marchand wrote:
> > On Thu, Jan 30, 2020 at 8:48 AM siddarth rai wrote:
> >> I have been using DPDK 19.08 and I notice the process VSZ is huge.
> >>
> >> I tried running the test PMD. It takes
On 04-Feb-20 12:07 PM, siddarth rai wrote:
Hi Anatoly,
You mentioned that the maximum size of mempool is limited.
Can you tell what is the limit and where is it specified?
Regards,
Siddarth
The mempool size itself isn't limited.
However, due to the nature of how memory subsystem works, ther
Hi Anatoly,
You mentioned that the maximum size of mempool is limited.
Can you tell what is the limit and where is it specified?
Regards,
Siddarth
On Tue, Feb 4, 2020 at 5:27 PM siddarth rai wrote:
> Hi,
>
> Thanks for the clarification
>
> Regards,
> Siddarth
>
> On Tue, Feb 4, 2020 at 4:43 P
Hi,
Thanks for the clarification
Regards,
Siddarth
On Tue, Feb 4, 2020 at 4:43 PM Burakov, Anatoly
wrote:
> On 04-Feb-20 10:55 AM, siddarth rai wrote:
> > Hi Anatoly,
> >
> > I don't need a secondary process.
>
> I understand that you don't, however that doesn't negate the fact that
> the code
On 04-Feb-20 10:55 AM, siddarth rai wrote:
Hi Anatoly,
I don't need a secondary process.
I understand that you don't, however that doesn't negate the fact that
the codepath expects that you do.
I tried out Julien's suggestion and set the param 'RTE_MAX_MEM_MB' value
to 8192 (the original
Hi Anatoly,
I don't need a secondary process.
I tried out Julien's suggestion and set the param 'RTE_MAX_MEM_MB' value to
8192 (the original value was over 500K). This works as a cap.
The virtual size dropped down to less than 8G. So this seems to be working
for me.
I have a few queries/concerns
On 30-Jan-20 8:51 AM, David Marchand wrote:
On Thu, Jan 30, 2020 at 8:48 AM siddarth rai wrote:
I have been using DPDK 19.08 and I notice the process VSZ is huge.
I tried running the test PMD. It takes 64G VSZ and if I use the
'--in-memory' option it takes up to 188G.
Is there anyway to disab
On 02-Feb-20 9:22 AM, David Marchand wrote:
On Thu, Jan 30, 2020 at 8:48 AM siddarth rai wrote:
Hi,
I have been using DPDK 19.08 and I notice the process VSZ is huge.
I tried running the test PMD. It takes 64G VSZ and if I use the
'--in-memory' option it takes up to 188G.
Is there anyway to
On Thu, Jan 30, 2020 at 8:48 AM siddarth rai wrote:
>
> Hi,
>
> I have been using DPDK 19.08 and I notice the process VSZ is huge.
>
> I tried running the test PMD. It takes 64G VSZ and if I use the
> '--in-memory' option it takes up to 188G.
>
> Is there anyway to disable allocation of such huge
order to configure
> RTE_MAX_MEM_MB are related parameters for your specific application.
>
> ---
> Julien Meunier
>
> > -Original Message-
> > From: dev On Behalf Of siddarth rai
> > Sent: Thursday, January 30, 2020 11:48 AM
> > To: David Marchand
>
your specific application.
---
Julien Meunier
> -Original Message-
> From: dev On Behalf Of siddarth rai
> Sent: Thursday, January 30, 2020 11:48 AM
> To: David Marchand
> Cc: Burakov, Anatoly ; dev
> Subject: Re: [dpdk-dev] Big spike in DPDK VSZ
>
> Hi,
>
> I did
Hi,
I did some further experiments and found out that version 18.02.2 doesn't
have the problem, but the 18.05.1 release has it.
Would really appreciate if someone can help, if there is a patch to get
over this issue in the DPDK code ?
This is becoming a huge practical issue for me as on multi NUM
On Thu, Jan 30, 2020 at 8:48 AM siddarth rai wrote:
> I have been using DPDK 19.08 and I notice the process VSZ is huge.
>
> I tried running the test PMD. It takes 64G VSZ and if I use the
> '--in-memory' option it takes up to 188G.
>
> Is there anyway to disable allocation of such huge VSZ in DPD
Hi,
I have been using DPDK 19.08 and I notice the process VSZ is huge.
I tried running the test PMD. It takes 64G VSZ and if I use the
'--in-memory' option it takes up to 188G.
Is there anyway to disable allocation of such huge VSZ in DPDK ?
This is resulting in huge core files and I suspect tha
16 matches
Mail list logo
