From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Walsh, Conor" <conor.walsh@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "web@dpdk.org" <web@dpdk.org>
Subject: RE: [PATCH v3] update Intel roadmap for 22.07
Date: Thu, 21 Apr 2022 13:03:30 +0000 [thread overview]
Message-ID: <DM6PR11MB3227859DF4D257A17059EB4BFCF49@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220421125554.10765-1-conor.walsh@intel.com>
> -----Original Message-----
> From: Walsh, Conor <conor.walsh@intel.com>
> Sent: Thursday, April 21, 2022 1:56 PM
> To: thomas@monjalon.net; Mcnamara, John <john.mcnamara@intel.com>
> Cc: web@dpdk.org; Walsh, Conor <conor.walsh@intel.com>
> Subject: [PATCH v3] update Intel roadmap for 22.07
>
> <!-- 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 to vhost
> +- vhost add async dequeue support for split ring
> +- vhost add small copy with CPU in DSA accelerated vhost
For consistency the first one of these would be better as:
vhost add thread-unsafe/thread-safe in-flight packets check
Apart from that:
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2022-04-21 13:05 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 [this message]
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=DM6PR11MB3227859DF4D257A17059EB4BFCF49@DM6PR11MB3227.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=conor.walsh@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).