From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 8BFCC5B38 for ; Fri, 8 Jun 2018 19:24:57 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jun 2018 10:24:56 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,490,1520924400"; d="scan'208";a="47852653" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by orsmga008.jf.intel.com with ESMTP; 08 Jun 2018 10:24:56 -0700 Received: from fmsmsx121.amr.corp.intel.com (10.18.125.36) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 8 Jun 2018 10:24:55 -0700 Received: from hasmsx108.ger.corp.intel.com (10.184.198.18) by fmsmsx121.amr.corp.intel.com (10.18.125.36) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 8 Jun 2018 10:24:55 -0700 Received: from HASMSX110.ger.corp.intel.com ([169.254.6.122]) by hasmsx108.ger.corp.intel.com ([169.254.9.94]) with mapi id 14.03.0319.002; Fri, 8 Jun 2018 20:24:53 +0300 From: "Rosen, Rami" To: "O'Driscoll, Tim" , "dev@dpdk.org" Thread-Topic: 18.08 Intel Roadmap Thread-Index: AdP9Z92J1fIyZQi5Q8OIvrfbdcbeBgB4e7gQ Date: Fri, 8 Jun 2018 17:24:52 +0000 Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F95A3CC8DD@HASMSX110.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BAB76EA5DD@IRSMSX108.ger.corp.intel.com> In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB76EA5DD@IRSMSX108.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMGNhNDA0ZmYtMWEyYS00MmJmLTg1YjgtY2YxNGUzNGRjMmRlIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiSUV6clRSeVRTdHUxWHhRY3JraThrWmk3cWN6dGVpUlNIa3NubGpkdzdReTFNN05Eckl3STJTcVZ5elRYRG5MeiJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [10.249.95.203] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] 18.08 Intel Roadmap X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 17:24:58 -0000 Hi, Tim, Thanks for posting the planned 18.08 roadmap, I hope other=20 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 q= ueues to include prior to starting the device. This >feature introduces a m= ore dynamic approach where the application can >also setup/reconfigure/tear= down queues after the device has been >started (on NICs where this is supp= orted in hardware). Maybe I am wrong, but isn't this already included in DPDK 18.05 ?=20 In DPDK 18.05 release notes:=20 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_e= th_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 s= et up at runtime need to be started explicitly by rte_eth_dev_rx_queue_star= t 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=20 was renamed to librte_ethdev in the meanwhile): http://dpdk.org/ml/archives/dev/2018-April/098461.html Regards, Rami Rosen