From: "Walsh, Conor" <conor.walsh@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"Mcnamara, John" <john.mcnamara@intel.com>
Cc: "web@dpdk.org" <web@dpdk.org>
Subject: RE: [PATCH v2] update Intel roadmap for 22.07
Date: Thu, 21 Apr 2022 12:56:46 +0000 [thread overview]
Message-ID: <PH0PR11MB52073C5707CC3E086C22A929FFF49@PH0PR11MB5207.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4343441.Wku2Vz74k6@thomas>
Thanks for your feedback Thomas.
I will send a v3 with the changes.
/Conor.
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday 13 April 2022 19:57
> To: Walsh, Conor <conor.walsh@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>
> Cc: web@dpdk.org
> Subject: Re: [PATCH v2] update Intel roadmap for 22.07
>
> Hi,
>
> I wanted to adjust this patch and merge it,
> but I am not sure about some points below.
>
> 04/04/2022 16:19, Conor Walsh:
> > Signed-off-by: Conor Walsh <conor.walsh@intel.com>
> > Acked-by: John McNamara <john.mcnamara@intel.com>
>
> [...]
> > +- dmadev library add telemetry support
>
> This line should not be in the Networking part.
>
> > +- ethdev library add protocol-based header split API
> > +- pipeline connection tracking improvements
> > +- pipeline packet mirroring support
> > +- pipeline hash support
> > +- pipeline default action arguments
> > <!-- Network drivers -->
> > - bonding Tx prepare
> > - mlx5 inline IPsec ESP crypto
> > @@ -26,19 +32,38 @@ This list is obviously neither complete nor
> guaranteed.
> > - qede initial support for next generation hardware
> > - qede flow API support
> > - spnic driver for Ramaxel devices
> > +- bbdev new PMD for Intel ACC101 device
> > +- DLB add support for DLB 2.5 QE weight hardware feature
> > +- DLB allow assignment of SW/HW credit quanta assignment on port usage
> hint
> > +- DLB allow dlb2 eventdev apps to use specific COS on per port basis
>
> These are not networking drivers, it should go below.
>
> > +- iavf PMD add raw pattern rte_flow support
> > +- iavf PMD add Rx timestamp offload support
> > +- ice PMD add header split support
> > +- ice PMD implement rte_tm to support 3 level QoS
> > +- Intel IPU SoC add new "idpf" PMD
> > +- Intel AFU PMD based on rawdev
> > <!-- Virtualisation -->
> > - vhost async dequeue for split ring and enable in vhost sample app
> > - vhost library statistics
> > - virtio hash reporting
> > +- Add thread-unsafe/thread-safe in-flight packets check
>
> Which library is it?
>
> > +- AESNI-MB PMD support chained mbuf for AES GCM and chachapoly
>
> This is for crypto group.
>
> > +- vhost add async dequeue support for split ring
> > +- vhost add small copy with CPU in DSA accelerated vhost
> > <!-- Network apps -->
> > - more info in dpdk-proc-info
> > <!-- Crypto -->
> > - qat with OpenSSL-3.0 library
> > +- openssl PMD add OpenSSL 3.0 lib support
> > +- QAT PMD remove deprecated dependency on openssl 1.x
> > +- QAT Gen 4 add asymmetric crypto algorithm support
> > <!-- Compress -->
> > <!-- Event -->
> > - event vector support in SW Rx eventdev adapter
> > - control adapter and RX adapter enhancements in DLB driver
> > <!-- Others -->
> > +- add eventdev_dump sample application
>
> I don't know why it is needed.
> In general it is better to have techboard approval for new examples.
>
> > +- EEPROM info dump add telemetric command
>
> Is it in a library?
>
next prev parent reply other threads:[~2022-04-21 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 12:24 [PATCH] " Conor Walsh
2022-03-24 12:39 ` Mcnamara, John
2022-03-24 14:19 ` Thomas Monjalon
2022-04-04 14:13 ` Conor Walsh
2022-04-04 14:19 ` [PATCH v2] " Conor Walsh
2022-04-12 14:17 ` Walsh, Conor
2022-04-13 18:56 ` Thomas Monjalon
2022-04-21 12:56 ` Walsh, Conor [this message]
2022-04-21 12:55 ` [PATCH v3] " Conor Walsh
2022-04-21 13:03 ` Mcnamara, John
2022-04-25 13:06 ` [PATCH v4] " Conor Walsh
2022-05-02 10:29 ` Thomas Monjalon
2022-05-02 10:37 ` Thomas Monjalon
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=PH0PR11MB52073C5707CC3E086C22A929FFF49@PH0PR11MB5207.namprd11.prod.outlook.com \
--to=conor.walsh@intel.com \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
/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).