DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Rosen, Rami" <rami.rosen@intel.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 18.08 Intel Roadmap
Date: Fri, 8 Jun 2018 17:24:52 +0000	[thread overview]
Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F95A3CC8DD@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB76EA5DD@IRSMSX108.ger.corp.intel.com>

Hi, Tim,
Thanks for posting the planned 18.08 roadmap, I hope other 
vendors will follow!

>Allow Setup/Reconfiguration/Tear Down of Queues at Run Time - >Currently, to configure a DPDK ethdev, the application specifies how >many Tx and Rx queues to include prior to starting the device. This >feature introduces a more dynamic approach where the application can >also setup/reconfigure/tear down queues after the device has been >started (on NICs where this is supported in hardware).

Maybe I am wrong, but isn't this already included in DPDK 18.05  ? 

In DPDK 18.05 release notes: 
https://dpdk.org/doc/guides/rel_notes/release_18_05.html

We have the following section:
...
ethdev: Runtime queue setup

rte_eth_rx_queue_setup and rte_eth_tx_queue_setup can be called after rte_eth_dev_start if the device supports runtime queue setup. The device driver can expose this capability through rte_eth_dev_info_get. A Rx or Tx queue set up at runtime need to be started explicitly by rte_eth_dev_rx_queue_start or rte_eth_dev_tx_queue_start.
...

And there is the following patchset from Qi, from April, adding support for runtime queue setup (in I40E and in the librte_ether library, which 
was renamed to librte_ethdev in the meanwhile):

http://dpdk.org/ml/archives/dev/2018-April/098461.html

Regards,
Rami Rosen

  reply	other threads:[~2018-06-08 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06  7:34 O'Driscoll, Tim
2018-06-08 17:24 ` Rosen, Rami [this message]
2018-06-08 17:35   ` Ferruh Yigit

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=9B0331B6EBBD0E4684FBFAEDA55776F95A3CC8DD@HASMSX110.ger.corp.intel.com \
    --to=rami.rosen@intel.com \
    --cc=dev@dpdk.org \
    --cc=tim.odriscoll@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).