From: Yongseok Koh <yskoh@mellanox.com>
To: olivier.matz@6wind.com, thomas@monjalon.net
Cc: dev@dpdk.org, arybchenko@solarflare.com,
konstantin.ananyev@intel.com, stephen@networkplumber.org,
Yongseok Koh <yskoh@mellanox.com>
Subject: [dpdk-dev] [PATCH] doc: announce removal of indirect mbuf check macro
Date: Thu, 24 May 2018 17:53:38 -0700 [thread overview]
Message-ID: <20180525005338.28773-1-yskoh@mellanox.com> (raw)
Link: http://dpdk.org/ml/archives/dev/2018-April/099476.html
Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
---
doc/guides/rel_notes/deprecation.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 1e2443c76..44da16445 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -42,6 +42,11 @@ Deprecation Notices
is defined in librte_sched in a non-generic way. The new generic format
will contain: queue ID, traffic class, color. Field size will not change.
+* mbuf: the macro ``RTE_MBUF_INDIRECT()`` will be removed in v18.08 and replaced
+ with ``RTE_MBUF_CLONED()``. As EXT_ATTACHED_MBUF is introduced in v18.05,
+ ``RTE_MBUF_INDIRECT()`` is no longer mutually exclusive with
+ ``RTE_MBUF_DIRECT()``. This change will fix the semantic inconsistency.
+
* ethdev: a new Tx and Rx offload API was introduced on 17.11.
In the new API, offloads are divided into per-port and per-queue offloads.
Offloads are disabled by default and enabled per application request.
--
2.11.0
next reply other threads:[~2018-05-25 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 0:53 Yongseok Koh [this message]
2018-05-25 1:20 ` [dpdk-dev] [PATCH v2] " Yongseok Koh
2018-05-25 6:34 ` Andrew Rybchenko
2018-05-25 7:20 ` Olivier Matz
2018-05-28 0:54 ` Thomas Monjalon
2018-05-27 4:36 ` Shahaf Shuler
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=20180525005338.28773-1-yskoh@mellanox.com \
--to=yskoh@mellanox.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.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).