DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] cryptodev: uninline parameter parsing
Date: Sat, 25 Jun 2016 15:24:15 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C96A09B@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1466860424-4155-1-git-send-email-thomas.monjalon@6wind.com>

Hi Thomas,

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Saturday, June 25, 2016 2:14 PM
> To: Doherty, Declan; De Lara Guarch, Pablo
> Cc: dev@dpdk.org
> Subject: [PATCH v2] cryptodev: uninline parameter parsing
> 
> There is no need to have this parsing inlined in the header.
> It brings kvargs dependency to every crypto drivers.
> The functions are moved into rte_cryptodev.c.
> 
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> ---
> v2:
> - remove kvargs dep in null PMD
> - add function in .map file
> ---
>  drivers/crypto/null/Makefile                   |  1 -
>  lib/librte_cryptodev/rte_cryptodev.c           | 91 ++++++++++++++++++++++++
>  lib/librte_cryptodev/rte_cryptodev.h           | 95 ++------------------------
>  lib/librte_cryptodev/rte_cryptodev_version.map |  7 ++
>  4 files changed, 102 insertions(+), 92 deletions(-)
> 
> diff --git a/drivers/crypto/null/Makefile b/drivers/crypto/null/Makefile
> index 573894f..35db8b1 100644
> --- a/drivers/crypto/null/Makefile
> +++ b/drivers/crypto/null/Makefile
> @@ -56,6 +56,5 @@ DEPDIRS-$(CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO)
> += lib/librte_eal
>  DEPDIRS-$(CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO) += lib/librte_mbuf
>  DEPDIRS-$(CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO) +=
> lib/librte_cryptodev
>  DEPDIRS-$(CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO) += lib/librte_ring
> -DEPDIRS-$(CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO) += lib/librte_kvargs
> 
>  include $(RTE_SDK)/mk/rte.lib.mk

[...]

>  /**
>   * Create a virtual crypto device
> diff --git a/lib/librte_cryptodev/rte_cryptodev_version.map
> b/lib/librte_cryptodev/rte_cryptodev_version.map
> index 41004e1..a08fd20 100644
> --- a/lib/librte_cryptodev/rte_cryptodev_version.map
> +++ b/lib/librte_cryptodev/rte_cryptodev_version.map
> @@ -32,3 +32,10 @@ DPDK_16.04 {
> 
>  	local: *;
>  };
> +
> +DPDK_16.07 {
> +	global:
> +
> +	rte_cryptodev_parse_vdev_init_params;

I think this function does not need to be public.
This function is only called in the PMDs, and the only public function
to initialize a crypto device is rte_eal_vdev_init.

> +
> +} DPDK_16.04;
> --
> 2.7.0

Also, could you remove the includes of rte_vargs.h in the PMDs,
as it is not needed (I think it was not necessary before either).

  reply	other threads:[~2016-06-25 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 15:47 [dpdk-dev] [PATCH] " Thomas Monjalon
2016-06-25 13:13 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2016-06-25 15:24   ` De Lara Guarch, Pablo [this message]
2016-06-26 16:31     ` Thomas Monjalon
2016-06-26 16:33   ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2016-06-27 10:20     ` De Lara Guarch, Pablo
2016-06-27 15:06       ` 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=E115CCD9D858EF4F90C690B0DCB4D8973C96A09B@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).