[dpdk-dev] 19.11 Intel Roadmap

[dpdk-dev] 19.11 Intel Roadmap

[O'Driscoll, Tim]

These are the features that we plan to submit for the 19.11 release:

Intel(r) Ethernet 810 Series Network Adapter Enhancements: Support for loading of device-specific Dynamic Device Personalization (DDP) profiles to support new protocols, rte_flow/flow director/switch filter updates to support DDP profiles, AVX2 versions of the ICE and IAVF PMDs to improve performance, multi-process support, RSS support via rte_flow, support for high/low priority flows via rte_flow, flexible descriptor support per Rx queue.

IPsec Enhancements: The rte_security API will be updated to support inline crypto statistics. A security association database will be added to the IPsec library. A new rte_security type (RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO) will be added to improve performance for IPsec with software crypto. The IPsec Security Gateway sample app will be updated to demonstrate the IPSec library's ability to support multiple IPsec sessions for the same SA (inline-crypto session plus lookaside-none).

Compression Enhancements: Intel(r) QuickAssist Technology support for stateful decompression, enhancements to the performance test tool including the ability to use external mbufs, and removal of the Experimental label from the compressdev API.

Crypto Enhancements: Increased Intel(r) QuickAssist Technology support for asymmetric (RSA) and symmetric (single-pass GCM) crypto operations, modifications to the cryptodev API to support sessionless asymmetric crypto.

Hierarchical QoS Scheduler Enhancements: The pipe (subscriber) configuration will be made more flexible by moving configuration data from the port to the sub-port level. Enhancements will also be made to provide better support for over-subscription, allowing unused bandwidth for a pipe to be redistributed to other pipes in the same sub-port.

ABI Stability: Agree and document new ABI stability policy. Implement code changes (hiding of internal structures etc.) to make ABI easier to maintain.

Virtio packed ring (introduced in Virtio 1.1 spec) performance optimisations.

Support graceful shutdown for the Intel(r) FPGA Programmable Acceleration Card N3000. The server will be able to gracefully shutdown and reload the card after certain errors (e.g. FPGA Die Temperature higher than Temperature Threshold or FPGA AUX Voltage lower than Voltage Threshold).

Extend Rawdev NTB PMD: The rawdev PMD for Non-Transparent Bridging will be extended to add a FIFO ring for Rx/Tx.

A sample application will be added for the Intel(r) QuickData Technology PMD (drivers/raw/ioat).

Intel PMDs will be updated to support RTE_ETH_DEV_CLOSE_REMOVE.

[dpdk-dev] which is the code base when submitting patch around end of September

[Hideyuki Yamashita]

Hello Experts,


Very basic question to create patch.

I am planning to post patch set which introduce new functionality (not
bug fix ).
Note that I will post the patch set on end of September.

Q1. 
If I post patch set to dev-ml, which is the code base?
Source code which is retrieved from "git clone" ?
Or tar ball of previous version like "dpdk-19.05.tar.gz"?

Q2. 
If review of the patch starts around October, when 
will the patch will be merged, if patch is good one.
19.11 LTS? or 20.02?
(Are there any rule or deadlines?)

Thanks in advance,
Hideyuki Yamashita
NTT TechnoCross

Re: [dpdk-dev] which is the code base when submitting patch around end of September

[Ye Xiaolong]

Hi,

On 08/09, Hideyuki Yamashita wrote:
>Hello Experts,
>
>
>Very basic question to create patch.
>
>I am planning to post patch set which introduce new functionality (not
>bug fix ).
>Note that I will post the patch set on end of September.

If your patch is targeted for 19.11 release, you need to send out your V1 patch
before proposal deadline 9/6, you can check the roadmap in http://core.dpdk.org/roadmap/.

>
>Q1. 
>If I post patch set to dev-ml, which is the code base?
>Source code which is retrieved from "git clone" ?
>Or tar ball of previous version like "dpdk-19.05.tar.gz"?
>

In most of cases, you should clone the main tree (git clone http://dpdk.org/git/dpdk)  
as the code base, and regularly rebase your patchset if you have new versions.

>Q2. 
>If review of the patch starts around October, when 
>will the patch will be merged, if patch is good one.
>19.11 LTS? or 20.02?
>(Are there any rule or deadlines?)

yes, please refer to the deadlines in the roadmap page.

Thanks,
Xiaolong

>
>Thanks in advance,
>Hideyuki Yamashita
>NTT TechnoCross
>

Re: [dpdk-dev] which is the code base when submitting patch around end of September

[Hideyuki Yamashita]

Hello Ye,

Thanks for your quick response.

I understand the basis.
I don't have much intention to push proposal to 19.11
right now.

Thanks again.

BR,
Hideyuki Yamashita
NTT TechnoCross

> Hi,
> 
> On 08/09, Hideyuki Yamashita wrote:
> >Hello Experts,
> >
> >
> >Very basic question to create patch.
> >
> >I am planning to post patch set which introduce new functionality (not
> >bug fix ).
> >Note that I will post the patch set on end of September.
> 
> If your patch is targeted for 19.11 release, you need to send out your V1 patch
> before proposal deadline 9/6, you can check the roadmap in http://core.dpdk.org/roadmap/.
> 
> >
> >Q1. 
> >If I post patch set to dev-ml, which is the code base?
> >Source code which is retrieved from "git clone" ?
> >Or tar ball of previous version like "dpdk-19.05.tar.gz"?
> >
> 
> In most of cases, you should clone the main tree (git clone http://dpdk.org/git/dpdk)  
> as the code base, and regularly rebase your patchset if you have new versions.
> 
> >Q2. 
> >If review of the patch starts around October, when 
> >will the patch will be merged, if patch is good one.
> >19.11 LTS? or 20.02?
> >(Are there any rule or deadlines?)
> 
> yes, please refer to the deadlines in the roadmap page.
> 
> Thanks,
> Xiaolong
> 
> >
> >Thanks in advance,
> >Hideyuki Yamashita
> >NTT TechnoCross
> >