DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: echaudro@redhat.com, jingjing.wu@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: adds mlockall() to fix pages
Date: Fri, 29 Sep 2017 10:27:43 +0100	[thread overview]
Message-ID: <00ad8865-a782-07cb-2ade-1cfec2cb456a@intel.com> (raw)
In-Reply-To: <2915a386-08ad-ca2e-4b33-2c001ec6c7dc@redhat.com>

On 29/09/2017 09:15, Eelco Chaudron wrote:
> On 29/09/17 10:07, Sergio Gonzalez Monroy wrote:
>> On 12/09/2017 14:08, Eelco Chaudron wrote:
>>> Call the mlockall() function, to attempt to lock all of its process
>>> memory into physical RAM, and preventing the kernel from paging any
>>> of its memory to disk.
>>>
>>> When using testpmd for performance testing, depending on the code path
>>> taken, we see a couple of page faults in a row. These faults effect
>>> the overall drop-rate of testpmd. On Linux the mlockall() call will
>>> prefault all the pages of testpmd (and the DPDK libraries if linked
>>> dynamically), even without LD_BIND_NOW.
>>>
>>> Signed-off-by: Eelco Chaudron <echaudro@redhat.com>
>>> ---
>>
>> When used for performance testing using hugepages or --no-huge option?
> This is independent of huge pages, its for the text (code) sections.

Understood.

Just for curiosity, how much drop-rate was observed?

Thanks,
Sergio

      reply	other threads:[~2017-09-29  9:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-12 13:08 Eelco Chaudron
2017-09-12 14:50 ` Aaron Conole
2017-09-12 20:14   ` Thomas Monjalon
2017-09-12 20:29     ` Aaron Conole
2017-09-12 22:13       ` Thomas Monjalon
2017-09-13  8:55         ` Eelco Chaudron
2017-09-13 12:28         ` Aaron Conole
2017-09-13  9:15 ` Maxime Coquelin
2017-09-13  9:39 ` Thomas Monjalon
2017-09-14  7:22   ` Eelco Chaudron
2017-09-19  7:28     ` Olivier MATZ
2017-09-21 12:24       ` Eelco Chaudron
2017-09-25  7:53         ` Olivier MATZ
2017-09-29  7:59           ` Eelco Chaudron
2017-09-29  8:07 ` Sergio Gonzalez Monroy
2017-09-29  8:15   ` Eelco Chaudron
2017-09-29  9:27     ` Sergio Gonzalez Monroy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=00ad8865-a782-07cb-2ade-1cfec2cb456a@intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=dev@dpdk.org \
    --cc=echaudro@redhat.com \
    --cc=jingjing.wu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).