DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: <declan.doherty@intel.com>, <sergio.gonzalez.monroy@intel.com>
Cc: <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 2/2] example/ipsec-secgw: add support for cryptodev_start
Date: Thu, 21 Jul 2016 16:24:04 +0530	[thread overview]
Message-ID: <1469098444-2156-2-git-send-email-hemant.agrawal@nxp.com> (raw)
In-Reply-To: <1469098444-2156-1-git-send-email-hemant.agrawal@nxp.com>

The usual device sequence is configure, queue setup and start.
Crypto device should be started before use.

Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
 examples/ipsec-secgw/ipsec-secgw.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/examples/ipsec-secgw/ipsec-secgw.c b/examples/ipsec-secgw/ipsec-secgw.c
index 1ca144b..302499c 100644
--- a/examples/ipsec-secgw/ipsec-secgw.c
+++ b/examples/ipsec-secgw/ipsec-secgw.c
@@ -1273,6 +1273,10 @@ cryptodevs_init(void)
 						&qp_conf, dev_conf.socket_id))
 				rte_panic("Failed to setup queue %u for "
 						"cdev_id %u\n",	0, cdev_id);
+		/* Start device */
+		if (rte_cryptodev_start(cdev_id))
+			rte_panic("Failed to start crypto dev for "
+						"cdev_id=%u\n", cdev_id);
 	}
 
 	printf("\n");
-- 
1.9.1

  reply	other threads:[~2016-07-21  5:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 10:54 [dpdk-dev] [PATCH 1/2] example/l2fwd-crypto: " Hemant Agrawal
2016-07-21 10:54 ` Hemant Agrawal [this message]
2016-07-22  9:44   ` [dpdk-dev] [PATCH v2 0/2] cryptodev_start fixes Thomas Monjalon
2016-07-22  9:44     ` [dpdk-dev] [PATCH v2 1/2] examples/l2fwd-crypto: call start function Thomas Monjalon
2016-07-22  9:44     ` [dpdk-dev] [PATCH v2 2/2] examples/ipsec-secgw: " Thomas Monjalon
2016-07-22 10:20     ` [dpdk-dev] [PATCH v2 0/2] cryptodev_start fixes De Lara Guarch, Pablo
2016-07-22 10:41       ` 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=1469098444-2156-2-git-send-email-hemant.agrawal@nxp.com \
    --to=hemant.agrawal@nxp.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=sergio.gonzalez.monroy@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).