DPDK patches and discussions
 help / color / mirror / Atom feed
From: Qi Zhang <qi.z.zhang@intel.com>
To: john.mcnamara@intel.com
Cc: dev@dpdk.org, Qi Zhang <qi.z.zhang@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc: update release notes.
Date: Thu, 10 May 2018 12:22:32 +0800	[thread overview]
Message-ID: <20180510042232.13924-1-qi.z.zhang@intel.com> (raw)

Add updates for runtime queue setup.

Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
---

v2:
- fix typo.

 doc/guides/rel_notes/release_18_05.rst | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/doc/guides/rel_notes/release_18_05.rst b/doc/guides/rel_notes/release_18_05.rst
index 718734852..589649121 100644
--- a/doc/guides/rel_notes/release_18_05.rst
+++ b/doc/guides/rel_notes/release_18_05.rst
@@ -183,7 +183,6 @@ New Features
   stats/xstats on shared memory from secondary process, and also pdump packets on
   those virtual devices.
 
-
 API Changes
 -----------
 
@@ -322,6 +321,12 @@ API Changes
   * ``rte_flow_create()`` API count action now requires the ``struct rte_flow_action_count``.
   * ``rte_flow_query()`` API parameter changed from action type to action structure.
 
+* ethdev: runtime queue setup:
+  * ``rte_eth_rx_queue_setup`` and ``rte_eth_rx_queue_setup`` can be called after
+    ``rte_eth_dev_start`` if device support runtime queue setup. Device driver can
+    expose this capability through ``rte_eth_dev_info_get``. A Rx or Tx queue be
+    setup at runtime need to be started explicitly by ``rte_eth_dev_rx_queue_start``
+    or ``rte_eth_dev_tx_queue_start``.
 
 ABI Changes
 -----------
-- 
2.13.6

             reply	other threads:[~2018-05-10  4:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10  4:22 Qi Zhang [this message]
2018-05-10  6:24 ` Tonghao Zhang
2018-05-10  6:45   ` Zhang, Qi Z

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=20180510042232.13924-1-qi.z.zhang@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@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).