From: Fan Zhang <roy.fan.zhang@intel.com>
To: dev@dpdk.org
Cc: yliu@fridaylinux.org, maxime.coquelin@redhat.com,
jianfeng.tan@intel.com, pablo.de.lara.guarch@intel.com,
zhihong.wang@intel.com, tiwei.bie@intel.com
Subject: [dpdk-dev] [RFC PATCH v2 5/7] config/common_base: add vhost_crypto configuration items
Date: Thu, 2 Nov 2017 20:10:57 +0000 [thread overview]
Message-ID: <20171102201059.2803-6-roy.fan.zhang@intel.com> (raw)
In-Reply-To: <20171102201059.2803-1-roy.fan.zhang@intel.com>
This patch adds the vhost_crypto related compile configuration items
to config/common_base. A new item
"CONFIG_RTE_LIBRTE_VHOST_CRYPTO_DATA_QUEUE_NO_COPY" is introduced
to turn on/off data queue no copy feature to vhost_crypto. This
feature is in experimental level so no gurantee it would work,
especially when kernel crypto framework and virtio-crypto driver
are used in the frontend.
Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
---
config/common_base | 1 +
1 file changed, 1 insertion(+)
diff --git a/config/common_base b/config/common_base
index d9471e8..79b3e3c 100644
--- a/config/common_base
+++ b/config/common_base
@@ -764,6 +764,7 @@ CONFIG_RTE_LIBRTE_PDUMP=y
# Compile vhost user library
#
CONFIG_RTE_LIBRTE_VHOST=n
+CONFIG_RTE_LIBRTE_VHOST_CRYPTO_DATA_QUEUE_NO_COPY=n
CONFIG_RTE_LIBRTE_VHOST_NUMA=n
CONFIG_RTE_LIBRTE_VHOST_DEBUG=n
--
2.9.5
next prev parent reply other threads:[~2017-11-02 20:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 16:09 [dpdk-dev] [RFC PATCH 0/6] lib/librte_vhost: introduce new vhost_user crypto backend support Fan Zhang
2017-11-02 16:09 ` [dpdk-dev] [RFC PATCH 1/6] lib/librte_vhost: add vhost_user private info structure Fan Zhang
2017-11-02 16:09 ` [dpdk-dev] [RFC PATCH 2/6] lib/librte_vhost: add virtio-crypto spec support Fan Zhang
2017-11-02 16:09 ` [dpdk-dev] [RFC PATCH 3/6] lib/librte_vhost: add vhost_user backend support Fan Zhang
2017-11-02 16:09 ` [dpdk-dev] [RFC PATCH 4/6] config/common_base: add vhost_crypto configuration items Fan Zhang
2017-11-02 16:09 ` [dpdk-dev] [RFC PATCH 5/6] lib/librte_vhost: update Makefile for vhost_crypto Fan Zhang
2017-11-02 16:09 ` [dpdk-dev] [RFC PATCH 6/6] example/vhost_crypto: add vhost_crypto sample application Fan Zhang
2017-11-02 20:10 ` [dpdk-dev] [RFC PATCH v2 0/7] lib/librte_vhost: introduce new vhost_user crypto backend support Fan Zhang
2017-11-02 20:10 ` [dpdk-dev] [RFC PATCH v2 1/7] lib/librte_vhost: add private data field Fan Zhang
2017-11-02 20:10 ` [dpdk-dev] [RFC PATCH v2 2/7] lib/librte_vhost: add vhost_user private info structure Fan Zhang
2017-11-02 20:10 ` [dpdk-dev] [RFC PATCH v2 3/7] lib/librte_vhost: add virtio-crypto spec support Fan Zhang
2017-11-02 20:10 ` [dpdk-dev] [RFC PATCH v2 4/7] lib/librte_vhost: add vhost_user backend support Fan Zhang
2017-11-02 20:10 ` Fan Zhang [this message]
2017-11-02 20:10 ` [dpdk-dev] [RFC PATCH v2 6/7] lib/librte_vhost: update Makefile for vhost_crypto Fan Zhang
2017-11-02 20:10 ` [dpdk-dev] [RFC PATCH v2 7/7] example/vhost_crypto: add vhost_crypto sample application Fan Zhang
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=20171102201059.2803-6-roy.fan.zhang@intel.com \
--to=roy.fan.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=tiwei.bie@intel.com \
--cc=yliu@fridaylinux.org \
--cc=zhihong.wang@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).