From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
thomas@monjalon.net
Subject: [dpdk-dev] [PATCH 2/2] doc: update release notes with info about memory changes
Date: Fri, 25 May 2018 14:41:03 +0100 [thread overview]
Message-ID: <28f51d457b24022cc9b9695688e3a962567a233b.1527255643.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <68f449f31b079aad4707cf6c9db8d1042861381d.1527255643.git.anatoly.burakov@intel.com>
In-Reply-To: <68f449f31b079aad4707cf6c9db8d1042861381d.1527255643.git.anatoly.burakov@intel.com>
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
doc/guides/rel_notes/release_18_05.rst | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
diff --git a/doc/guides/rel_notes/release_18_05.rst b/doc/guides/rel_notes/release_18_05.rst
index 40eec3a..84b7434 100644
--- a/doc/guides/rel_notes/release_18_05.rst
+++ b/doc/guides/rel_notes/release_18_05.rst
@@ -41,6 +41,40 @@ New Features
Also, make sure to start the actual text at the margin.
=========================================================
+* **Reworked memory subsystem.**
+
+ Memory subsystem has been reworked to support new functionality.
+
+ On Linux, support for reserving/unreserving hugepage memory at runtime was
+ added, so applications no longer need to pre-reserve memory at startup. Due to
+ reorganized internal workings of memory subsystem, any memory allocated
+ through ``rte_malloc()`` or ``rte_memzone_reserve()`` is no longer guaranteed
+ to be IOVA-contiguous.
+
+ This functionality has introduced the following changes:
+
+ * ``rte_eal_get_physmem_layout()`` was removed
+ * A new flag for memzone reservation (``RTE_MEMZONE_IOVA_CONTIG``) was added
+ to ensure reserved memory will be IOVA-contiguous, for use with device
+ drivers and other cases requiring such memory
+ * New callbacks for memory allocation/deallocation events, allowing user (or
+ drivers) to be notified of new memory being allocated or deallocated
+ * New callbacks for validating memory allocations above specified limit,
+ allowing user to permit or deny memory allocations
+ * A new command-line switch ``--legacy-mem`` to enable EAL behavior similar to
+ how older versions of DPDK worked (memory segments that are IOVA-contiguous,
+ but hugepages are reserved at startup only, and can never be released)
+ * A new command-line switch ``--single-file-segments`` to put all memory
+ segments within a segment list in a single file
+ * A set of convenience function calls to look up and iterate over allocated
+ memory segments
+ * ``-m`` and ``--socket-mem`` command-line arguments now carry an additional
+ meaning and mark pre-reserved hugepages as "unfree-able", thereby acting as
+ a mechanism guaranteeing minimum availability of hugepage memory to the
+ application
+
+ Reserving/unreserving memory at runtime is not currently supported on FreeBSD.
+
* **Added bucket mempool driver.**
Added bucket mempool driver which provides a way to allocate contiguous
--
2.7.4
next prev parent reply other threads:[~2018-05-25 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 13:41 [dpdk-dev] [PATCH 1/2] doc: update documentation for memory subsystem Anatoly Burakov
2018-05-25 13:41 ` Anatoly Burakov [this message]
2018-05-28 0:17 ` Thomas Monjalon
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=28f51d457b24022cc9b9695688e3a962567a233b.1527255643.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=thomas@monjalon.net \
/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).