DPDK patches and discussions
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Hobywan Kenoby <hobywank@hotmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 2.3 Roadmap
Date: Tue, 1 Dec 2015 11:52:56 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA67470B45@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <DBXPR06MB303F7F4D4EE49D2631AE704C0000@DBXPR06MB303.eurprd06.prod.outlook.com>


> -----Original Message-----
> From: Hobywan Kenoby [mailto:hobywank@hotmail.com]
> Sent: Monday, November 30, 2015 10:30 PM
> To: O'Driscoll, Tim; dev@dpdk.org
> Subject: Re: 2.3 Roadmap
> 
> 
> Hi,
> 
> CAT And CDP technologies look very intriguing.... Could you elaborate a
> little on those?

We're working on a white paper which should be available soon. In the meantime, there's more information on these technologies at:
https://www-ssl.intel.com/content/www/us/en/communications/cache-monitoring-cache-allocation-technologies.html
https://01.org/packet-processing/cache-monitoring-technology-memory-bandwidth-monitoring-cache-allocation-technology-code-and-data


Tim

> 
> -HK
> ________________________________________
> From: dev <dev-bounces@dpdk.org> on behalf of O'Driscoll, Tim
> <tim.odriscoll@intel.com>
> Sent: Monday, November 30, 2015 9:50:58 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] 2.3 Roadmap
> 
> As we're nearing the completion of the 2.2 release, I'd like to start a
> discussion on plans for 2.3. To kick this off, below are the features
> that we're hoping to submit for this release.
> 
> If others are prepared to contribute their plans, then we could build a
> complete view of the release which Thomas can maintain on the dpdk.org
> roadmap page, and make sure we're not duplicating work.
> 
> 
> IPsec Sample Application: A sample application will be created which
> will show how DPDK and the new cryptodev API can be used to implement
> IPsec. Use of the cryptodev API will allow either hardware or software
> encryption to be used. IKE will not be implemented so the SA/SP DBs will
> be statically configured.
> 
> Cryptodev Support for SNOW 3G: The cryptodev API, and the hardware and
> software crypto PMDs that it supports, will be enhanced to support the
> SNOW 3G cipher.
> 
> External Mempool Manager: SoCs and some software applications that use
> DPDK have their own memory allocation capabilities. This feature will
> allow DPDK to work with an external mempool manager.
> 
> Packet Framework (Edge Router Use Case):
> - Further performance tuning for the vPE use case.
> - Support for load balancing within a pipeline.
> - Support for CPU utilization measurements within a pipeline.
> - Improvements for the functional pipelines, tables and ports.
> 
> Ethdev Enhancements: Merge parts of the Packet Framework ports library
> into ethdev so they can be used without the Packet Framework. The
> initial focus is to add support for buffered TX to ethdev.
> 
> Live Migration: The main infrastructure to support live migration of VMs
> was implemented over the last few DPDK releases via the Link Bonding and
> PCI Hot Plug features. This feature will involve further investigation,
> prototyping and enhancements to improve live migration support in DPDK.
> 
> Tcpdump Support: Support for tcpdump will be added to DPDK. This will
> improve usability and debugging of DPDK applications.
> 
> Increase Next Hops for LPM (IPv4): The number of next hops for IPv4 LPM
> is currently limited to 256. This will be extended to allow a greater
> number of next hops.
> 
> Fm10k Enhancements: FTAG based forwarding, and performance tuning
> 
> Support Intel Resource Director Technology: A library will be added to
> DPDK to support the following Intel CPU technologies:
> - CAT - Cache Allocation Technology (LLC aka L3)
> - CDP - Code Data Prioritization (extension of CAT)
> - CMT - Cache Monitoring Technology (LLC)
> - MBM - Memory Bandwidth Monitoring, to local and remote RAM
> These technologies are currently available via cgroups and perf, but
> this feature will provide closer integration with DPDK and a sample
> application showing how they can be used.
> 
> I40e Enhancements:
> - Flow Director input set Alignment
> - Ethertype configuration for QinQ support
> - Flow Director Support for Tunnels (QinQ, GRE/NVGRE, VXLAN)
> - Flow Director Support for IP Proto and IP TOS
> - VEB switching
> - Floating VEB
> - IPGRE Support
> - Set VF MAC address
> - Rework PCIe extended tag enabling by using DPDK interfaces
> 
> Virtio/Vhost Enhancements:
> - Virtio 1.0 support
> - Vhost software TSO
> - Vhost/virtio performance tuning
> 
> Container Enhancements:
> - Virtio for containers
> - Hugetlbfs mount point size
> - Cgroup resource awareness
> - Enable short-lived DPDK applications
> 
> Generic Tunneling API:
> - Implement virtual flow device framework
> - Implement generic virtual device management APIs, including the
> following callback functions:
>   - flow_ethdev_start/stop/configure/close/info_get
>   - ethdev_rx/tx_queue_setup/release
>   - flow_ethdev_tunnel_configure/setup/destroy
>   - flow_ethdev_tunnel_pkt_decap/encap
> - Implement flow device PMD drive APIs
>   - rte_eth_flow_dev_create/remove/ others
> - Integrate VXLAN protocol (including VXLAN decap/encap optimization)
> into this framework only on i40e.
> 
> 
> Tim

  reply	other threads:[~2015-12-01 11:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 20:50 O'Driscoll, Tim
2015-11-30 21:50 ` Thomas Monjalon
2015-11-30 22:19 ` Dave Neary
2015-12-01 11:57   ` O'Driscoll, Tim
2015-11-30 22:30 ` Hobywan Kenoby
2015-12-01 11:52   ` O'Driscoll, Tim [this message]
2015-11-30 22:53 ` Kyle Larose
2015-12-01  1:16   ` Stephen Hemminger
2015-12-01 10:03     ` Bruce Richardson
2015-12-01 11:26       ` Yoshinobu Inoue
2015-12-01 11:58         ` Bruce Richardson
2015-12-01 13:42           ` Matthew Hall
2015-12-01 14:45             ` Kyle Larose
2015-12-01 19:28               ` Matthew Hall
2015-12-02  0:53           ` Yoshinobu Inoue
2015-12-01 14:27       ` Panu Matilainen
2015-12-01 14:48         ` Vincent JARDIN
2015-12-01 14:58           ` Panu Matilainen
2015-12-01 15:16             ` Christian Ehrhardt
2015-12-01 15:19             ` Bruce Richardson
2015-12-01 15:31               ` Aaron Conole
2015-12-01 15:54                 ` Richardson, Bruce
2015-12-02  1:38                   ` Wiles, Keith
2015-12-02  2:42                     ` Matthew Hall
2015-12-01 19:32                 ` Matthew Hall
2015-12-02 11:24           ` Neil Horman
2015-12-01 12:59 ` Matthew Hall
2015-12-01 13:16   ` O'Driscoll, Tim
2015-12-01 13:44     ` Matthew Hall
2015-12-01 13:57       ` Bruce Richardson
2015-12-01 19:49         ` Matthew Hall
2015-12-02 12:35           ` Bruce Richardson
2015-12-02 15:47             ` Matthew Hall

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=26FA93C7ED1EAA44AB77D62FBE1D27BA67470B45@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=dev@dpdk.org \
    --cc=hobywank@hotmail.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).