From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, chenbo.xia@intel.com, ian.stokes@intel.com
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-dev] [PATCH v2 2/4] examples/vhost_crypto: use vhost async-copy flag
Date: Mon, 28 Sep 2020 11:17:10 +0200 [thread overview]
Message-ID: <20200928091712.7946-3-maxime.coquelin@redhat.com> (raw)
In-Reply-To: <20200928091712.7946-1-maxime.coquelin@redhat.com>
The crypto backend uses RTE_VHOST_USER_DEQUEUE_ZERO_COPY only
for the shared areas to be populated at mmap time. It does
not use the other mechanisms the feature provides.
Now that RTE_VHOST_USER_DEQUEUE_ZERO_COPY is being removed,
let's use RTE_VHOST_USER_ASYNC_COPY instead which does the
same thing.
Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Reviewed-by: Chenbo Xia <chenbo.xia@intel.com>
---
examples/vhost_crypto/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/examples/vhost_crypto/main.c b/examples/vhost_crypto/main.c
index 1d7ba94196..4bdd12f695 100644
--- a/examples/vhost_crypto/main.c
+++ b/examples/vhost_crypto/main.c
@@ -588,7 +588,7 @@ main(int argc, char *argv[])
for (j = 0; j < lo->nb_sockets; j++) {
ret = rte_vhost_driver_register(lo->socket_files[j],
- RTE_VHOST_USER_DEQUEUE_ZERO_COPY);
+ RTE_VHOST_USER_ASYNC_COPY);
if (ret < 0) {
RTE_LOG(ERR, USER1, "socket %s already exists\n",
lo->socket_files[j]);
--
2.26.2
next prev parent reply other threads:[~2020-09-28 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 9:17 [dpdk-dev] [PATCH v2 0/4] vhost: remove dequeue zero-copy support Maxime Coquelin
2020-09-28 9:17 ` [dpdk-dev] [PATCH v2 1/4] net/vhost: " Maxime Coquelin
2020-09-28 11:07 ` Xia, Chenbo
2020-09-28 9:17 ` Maxime Coquelin [this message]
2020-09-28 9:17 ` [dpdk-dev] [PATCH v2 3/4] examples/vhost: " Maxime Coquelin
2020-09-28 9:17 ` [dpdk-dev] [PATCH v2 4/4] vhost: " Maxime Coquelin
2020-09-28 11:14 ` Xia, Chenbo
2020-09-30 16:21 ` [dpdk-dev] [PATCH v2 0/4] " Maxime Coquelin
2020-09-30 20:56 ` Ferruh Yigit
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=20200928091712.7946-3-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=ian.stokes@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).