From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples/vhost_crypto: add multi-core support
Date: Wed, 12 Sep 2018 09:25:05 +0200 [thread overview]
Message-ID: <b71138d2-1d16-f56f-2499-b451f6c264d3@redhat.com> (raw)
In-Reply-To: <20180622123605.10241-1-roy.fan.zhang@intel.com>
Hi Fan,
On 06/22/2018 02:36 PM, Fan Zhang wrote:
> Originally vhost_crypto sample application only supports single
> core. This patch adds the multi-core support with more flexible
> options.
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
> doc/guides/sample_app_ug/vhost_crypto.rst | 26 +-
> examples/vhost_crypto/main.c | 480 +++++++++++++++++-------------
> 2 files changed, 282 insertions(+), 224 deletions(-)
>
Sorry for the late review.
The patch looks good to me:
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Maxime
next prev parent reply other threads:[~2018-09-12 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 12:36 Fan Zhang
2018-07-23 11:26 ` De Lara Guarch, Pablo
2018-09-12 7:25 ` Maxime Coquelin [this message]
2018-09-13 8:37 ` Maxime Coquelin
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=b71138d2-1d16-f56f-2499-b451f6c264d3@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@intel.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).