From: Thomas Monjalon <thomas@monjalon.net>
To: Conor Walsh <conor.walsh@intel.com>
Cc: john.mcnamara@intel.com, web@dpdk.org
Subject: Re: [PATCH v4] update Intel roadmap for 22.07
Date: Mon, 02 May 2022 12:29:39 +0200 [thread overview]
Message-ID: <10280950.T7Z3S40VBb@thomas> (raw)
In-Reply-To: <20220425130652.4736-1-conor.walsh@intel.com>
I've still some doubts about some items,
but this patch is pending for long,
so I will adapt it with my understanding.
See some questions below. Please could you reply to make things clear?
25/04/2022 15:06, Conor Walsh:
> v2:
> - Drop removal of "qat with OpenSSL-3.0 library"
So there will be a change in qat for OpenSSL 3 ?
> +- Intel IPU SoC add new "idpf" PMD
> +- Intel AFU PMD based on rawdev
Not clear what AFU is. Is it for the IPU above?
We already have an AFU PMD raw/ifpga.
> <!-- Virtualisation -->
> - vhost async dequeue for split ring and enable in vhost sample app
> - vhost library statistics
> - virtio hash reporting
> +- vhost add thread-unsafe/thread-safe in-flight packets check
> +- vhost add async dequeue support for split ring
This item is redundant with the first one of this section.
next prev parent reply other threads:[~2022-05-02 10:29 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
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 [this message]
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=10280950.T7Z3S40VBb@thomas \
--to=thomas@monjalon.net \
--cc=conor.walsh@intel.com \
--cc=john.mcnamara@intel.com \
--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).