From: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
To: dev@dpdk.org
Cc: jerinj@marvell.com, gage.eads@intel.com,
harry.van.haaren@intel.com, mdr@ashroe.eu, nhorman@tuxdriver.com,
nikhil.rao@intel.com, erik.g.carrillo@intel.com,
abhinandan.gujjar@intel.com, pbhagavatula@marvell.com,
hemant.agrawal@nxp.com, mattias.ronnblom@ericsson.com,
peter.mccarthy@intel.com, "McDaniel,
Timothy" <timothy.mcdaniel@intel.com>
Subject: [dpdk-dev] [PATCH] doc: announce changes to eventdev public data structures
Date: Thu, 2 Jul 2020 17:13:57 -0500 [thread overview]
Message-ID: <1593728037-15717-1-git-send-email-timothy.mcdaniel@intel.com> (raw)
From: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
Signed-off-by: McDaniel, Timothy <timothy.mcdaniel@intel.com>
---
doc/guides/rel_notes/deprecation.rst | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index d1034f6..6af9b40 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -130,3 +130,31 @@ Deprecation Notices
Python 2 support will be completely removed in 20.11.
In 20.08, explicit deprecation warnings will be displayed when running
scripts with Python 2.
+
+* eventdev: Three public data structures will be updated in 20.11;
+ ``rte_event_dev_info``, ``rte_event_dev_config``, and
+ ``rte_event_port_conf``.
+ Two new members will be added to the ``rte_event_dev_info`` struct.
+ The first, max_event_port_links, will be a uint8_t, and represents the
+ maximum number of queues that can be linked to a single event port by
+ this device. The second, max_single_link_event_port_queue_pairs, will be a
+ uint8_t, and represents the maximum number of event ports and queues that
+ are optimized for (and only capable of) single-link configurations
+ supported by this device. These ports and queues are not accounted for in
+ max_event_ports or max_event_queues.
+ One new member will be added to the ``rte_event_dev_config`` struct. The
+ nb_single_link_event_port_queues member will be a uint8_t, and will
+ represent the number of event ports and queues that will be singly-linked
+ to each other. These are a subset of the overall event ports and queues.
+ This value cannot exceed nb_event_ports or nb_event_queues. If the
+ device has ports and queues that are optimized for single-link usage, this
+ field is a hint for how many to allocate; otherwise, regular event ports and
+ queues can be used.
+ Finally, the ``rte_event_port_conf`` struct will be
+ modified as follows. The uint8_t implicit_release_disabled field
+ will be replaced by a uint32_t event_port_cfg field. The new field will
+ initially have two bits assigned. RTE_EVENT_PORT_CFG_DISABLE_IMPL_REL
+ will have the same meaning as implicit_release_disabled. The second bit,
+ RTE_EVENT_PORT_CFG_SINGLE_LINK will be set if the event port links only
+ to a single event queue.
+
--
1.7.10
next reply other threads:[~2020-07-02 22:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 22:13 McDaniel, Timothy [this message]
2020-07-30 16:33 ` McDaniel, Timothy
2020-07-30 18:48 ` Jerin Jacob
2020-07-31 18:51 ` McDaniel, Timothy
2020-07-31 19:03 ` Jerin Jacob
2020-07-31 19:31 ` McDaniel, Timothy
2020-08-03 6:09 ` Jerin Jacob
2020-08-03 17:55 ` [dpdk-dev] [PATCH] doc: eventdev ABI change to support DLB PMD McDaniel, Timothy
2020-08-04 7:38 ` Jerin Jacob
2020-08-04 15:44 ` Hemant Agrawal
2020-08-05 23:39 ` Thomas Monjalon
2020-08-07 16:21 ` McDaniel, Timothy
2020-08-04 13:46 ` Van Haaren, Harry
2020-08-05 9:36 ` [dpdk-dev] [PATCH] doc: announce changes to eventdev public data structures Kinsella, Ray
2020-08-05 23:46 ` 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=1593728037-15717-1-git-send-email-timothy.mcdaniel@intel.com \
--to=timothy.mcdaniel@intel.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=gage.eads@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=nikhil.rao@intel.com \
--cc=pbhagavatula@marvell.com \
--cc=peter.mccarthy@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).