From: Eelco Chaudron <echaudro@redhat.com>
To: john.mcnamara@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] doc: Adds reference to use mlockall() in the Programmer's guide
Date: Fri, 29 Sep 2017 14:50:45 +0200 [thread overview]
Message-ID: <138d85856e7b5c6c09abfccdb885927458120be8.1506689397.git.echaudro@redhat.com> (raw)
When I was adding mlockall() to the testpmd application it was
suggested to add a reference to the use case of mlockall().
Signed-off-by: Eelco Chaudron <echaudro@redhat.com>
---
doc/guides/prog_guide/writing_efficient_code.rst | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/doc/guides/prog_guide/writing_efficient_code.rst b/doc/guides/prog_guide/writing_efficient_code.rst
index 8223aceea..3975026ce 100644
--- a/doc/guides/prog_guide/writing_efficient_code.rst
+++ b/doc/guides/prog_guide/writing_efficient_code.rst
@@ -105,6 +105,20 @@ meaning that if all memory access operations are done on the first channel only,
By default, the :ref:`Mempool Library <Mempool_Library>` spreads the addresses of objects among memory channels.
+Locking memory pages
+~~~~~~~~~~~~~~~~~~~~
+The underlying operating system is allowed to load/unload memory pages at its own discretion.
+These page loads could impact the performance, as the process is on hold when the kernel fetches them.
+
+To avoid these you could pre-load, and lock them into memory with the mlockall() call.
+
+.. code-block:: c
+
+ if (mlockall(MCL_CURRENT | MCL_FUTURE)) {
+ RTE_LOG(NOTICE, USER1, "mlockall() failed with error \"%s\"\n",
+ strerror(errno));
+ }
+
Communication Between lcores
----------------------------
--
2.13.6
next reply other threads:[~2017-09-29 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 12:50 Eelco Chaudron [this message]
2017-09-29 15:44 ` Mcnamara, John
2017-10-02 10:22 ` Eelco Chaudron
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=138d85856e7b5c6c09abfccdb885927458120be8.1506689397.git.echaudro@redhat.com \
--to=echaudro@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).