From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net
Subject: [dpdk-dev] [PATCH 2/2] memzone: clarify support for zero-length memzones
Date: Fri, 25 May 2018 14:39:45 +0100 [thread overview]
Message-ID: <cc0b9dc95f4d3060e5cffb07c2fc840ca0bc9583.1527255565.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <693c688e4189c1f7cb131ab76a287743011743b9.1527255565.git.anatoly.burakov@intel.com>
In-Reply-To: <693c688e4189c1f7cb131ab76a287743011743b9.1527255565.git.anatoly.burakov@intel.com>
Currently, memzone allocation with length set to 0 that are also
IOVA-contiguous is not supported. Document this limitation.
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
lib/librte_eal/common/include/rte_memzone.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/lib/librte_eal/common/include/rte_memzone.h b/lib/librte_eal/common/include/rte_memzone.h
index a4c9bd6..ef370fa 100644
--- a/lib/librte_eal/common/include/rte_memzone.h
+++ b/lib/librte_eal/common/include/rte_memzone.h
@@ -81,6 +81,9 @@ struct rte_memzone {
* memzones from memory that is already available. It will not trigger any
* new allocations.
*
+ * @note Reserving IOVA-contiguous memzones with len set to 0 is not currently
+ * supported.
+ *
* @param name
* The name of the memzone. If it already exists, the function will
* fail and return NULL.
@@ -138,6 +141,9 @@ const struct rte_memzone *rte_memzone_reserve(const char *name,
* memzones from memory that is already available. It will not trigger any
* new allocations.
*
+ * @note Reserving IOVA-contiguous memzones with len set to 0 is not currently
+ * supported.
+ *
* @param name
* The name of the memzone. If it already exists, the function will
* fail and return NULL.
@@ -200,6 +206,9 @@ const struct rte_memzone *rte_memzone_reserve_aligned(const char *name,
* memzones from memory that is already available. It will not trigger any
* new allocations.
*
+ * @note Reserving IOVA-contiguous memzones with len set to 0 is not currently
+ * supported.
+ *
* @param name
* The name of the memzone. If it already exists, the function will
* fail and return NULL.
--
2.7.4
next prev parent reply other threads:[~2018-05-25 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 13:39 [dpdk-dev] [PATCH 1/2] mem: document callbacks not being supported in some cases Anatoly Burakov
2018-05-25 13:39 ` Anatoly Burakov [this message]
2018-05-27 23:48 ` [dpdk-dev] [PATCH 2/2] memzone: clarify support for zero-length memzones 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=cc0b9dc95f4d3060e5cffb07c2fc840ca0bc9583.1527255565.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--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).