DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jay Zhou <jianjay.zhou@huawei.com>
To: <dev@dpdk.org>
Cc: <maxime.coquelin@redhat.com>, <pablo.de.lara.guarch@intel.com>,
	<ferruh.yigit@intel.com>, <jianfeng.tan@intel.com>,
	<roy.fan.zhang@intel.com>, <arei.gonglei@huawei.com>,
	<weidong.huang@huawei.com>, <wangxinxin.wang@huawei.com>,
	<jianjay.zhou@huawei.com>
Subject: [dpdk-dev] [PATCH] compat: add virtio crypto header file
Date: Sat, 14 Apr 2018 17:26:54 +0800	[thread overview]
Message-ID: <1523698014-29444-1-git-send-email-jianjay.zhou@huawei.com> (raw)

Moving the virtio crypto header file from vhost lib to compat lib,
then this header file can be shared between vhost crypto backend and
virtio crypto PMD.

Signed-off-by: Jay Zhou <jianjay.zhou@huawei.com>
---
 lib/librte_compat/Makefile                          | 3 ++-
 lib/librte_compat/meson.build                       | 2 +-
 lib/{librte_vhost => librte_compat}/virtio_crypto.h | 0
 lib/librte_vhost/vhost_crypto.c                     | 2 +-
 4 files changed, 4 insertions(+), 3 deletions(-)
 rename lib/{librte_vhost => librte_compat}/virtio_crypto.h (100%)

diff --git a/lib/librte_compat/Makefile b/lib/librte_compat/Makefile
index 0c57533c1..5f78824c1 100644
--- a/lib/librte_compat/Makefile
+++ b/lib/librte_compat/Makefile
@@ -35,6 +35,7 @@ include $(RTE_SDK)/mk/rte.vars.mk
 LIBABIVER := 1
 
 # install includes
-SYMLINK-y-include := rte_compat.h
+SYMLINK-y-include += rte_compat.h
+SYMLINK-y-include += virtio_crypto.h
 
 include $(RTE_SDK)/mk/rte.install.mk
diff --git a/lib/librte_compat/meson.build b/lib/librte_compat/meson.build
index 82c7eea55..28762288e 100644
--- a/lib/librte_compat/meson.build
+++ b/lib/librte_compat/meson.build
@@ -2,7 +2,7 @@
 # Copyright(c) 2017 Intel Corporation
 
 
-install_headers('rte_compat.h')
+install_headers('rte_compat.h', 'virtio_crypto.h')
 
 set_variable('dep_rte_compat',
 	declare_dependency(include_directories: include_directories('.')))
diff --git a/lib/librte_vhost/virtio_crypto.h b/lib/librte_compat/virtio_crypto.h
similarity index 100%
rename from lib/librte_vhost/virtio_crypto.h
rename to lib/librte_compat/virtio_crypto.h
diff --git a/lib/librte_vhost/vhost_crypto.c b/lib/librte_vhost/vhost_crypto.c
index c154ef673..6e1f5eda5 100644
--- a/lib/librte_vhost/vhost_crypto.c
+++ b/lib/librte_vhost/vhost_crypto.c
@@ -6,11 +6,11 @@
 #include <rte_jhash.h>
 #include <rte_mbuf.h>
 #include <rte_cryptodev.h>
+#include <virtio_crypto.h>
 
 #include "rte_vhost_crypto.h"
 #include "vhost.h"
 #include "vhost_user.h"
-#include "virtio_crypto.h"
 
 #define INHDR_LEN		(sizeof(struct virtio_crypto_inhdr))
 #define IV_OFFSET		(sizeof(struct rte_crypto_op) + \
-- 
2.14.2

             reply	other threads:[~2018-04-14  9:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-14  9:26 Jay Zhou [this message]
2018-04-16 11:27 ` Zhang, Roy Fan

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=1523698014-29444-1-git-send-email-jianjay.zhou@huawei.com \
    --to=jianjay.zhou@huawei.com \
    --cc=arei.gonglei@huawei.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jianfeng.tan@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=wangxinxin.wang@huawei.com \
    --cc=weidong.huang@huawei.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).