From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: <dev@dpdk.org>
Cc: <thomas.monjalon@6wind.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-dev] [PATCH] doc: update release notes for I/O device memory access API
Date: Thu, 19 Jan 2017 11:13:21 +0530 [thread overview]
Message-ID: <1484804601-26531-1-git-send-email-jerin.jacob@caviumnetworks.com> (raw)
Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
---
doc/guides/rel_notes/release_17_02.rst | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/doc/guides/rel_notes/release_17_02.rst b/doc/guides/rel_notes/release_17_02.rst
index 0ecd720..eb0e3c0 100644
--- a/doc/guides/rel_notes/release_17_02.rst
+++ b/doc/guides/rel_notes/release_17_02.rst
@@ -193,6 +193,19 @@ New Features
See the :ref:`Elastic Flow Distributor Library <Efd_Library>` documentation in
the Programmers Guide document, for more information.
+* **Added generic EAL API for I/O device memory read/write operations.**
+
+ This API introduces 8-bit, 16-bit, 32bit, 64bit I/O device
+ memory read/write operations along with the relaxed versions.
+
+ The weakly-ordered machine like ARM needs additional I/O barrier for
+ device memory read/write access over PCI bus.
+ By introducing the EAL abstraction for I/O device memory read/write access,
+ The drivers can access I/O device memory in architecture-agnostic manner.
+ The relaxed version does not have additional I/O memory barrier, useful in
+ accessing the device registers of integrated controllers which
+ implicitly strongly ordered with respect to memory access.
+
Resolved Issues
---------------
--
2.5.5
next reply other threads:[~2017-01-19 5:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 5:43 Jerin Jacob [this message]
2017-01-19 17:35 ` Mcnamara, John
2017-01-30 18:02 ` 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=1484804601-26531-1-git-send-email-jerin.jacob@caviumnetworks.com \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).