All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fan Zhang <roy.fan.zhang@intel.com>
To: dev@dpdk.org
Cc: pablo.de.lara.guarch@intel.com, stable@dpdk.com
Subject: [PATCH] crypto/scheduler: fix slave init attach
Date: Wed, 19 Apr 2017 14:42:17 +0100	[thread overview]
Message-ID: <1492609337-44733-1-git-send-email-roy.fan.zhang@intel.com> (raw)

Fixes: 881851676940 ("crypto/scheduler: improve commandline parsing")

This patch fix the slaves attaching initially.

Originally, the scheduler will try to attach the slaves passed by the
cmdline option in the initial stage, this may break the sequence
of the slaves inside the scheduler.

Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
---
 drivers/crypto/scheduler/scheduler_pmd.c | 21 ---------------------
 1 file changed, 21 deletions(-)

diff --git a/drivers/crypto/scheduler/scheduler_pmd.c b/drivers/crypto/scheduler/scheduler_pmd.c
index f2a1d2a..2a92d1e 100644
--- a/drivers/crypto/scheduler/scheduler_pmd.c
+++ b/drivers/crypto/scheduler/scheduler_pmd.c
@@ -160,27 +160,6 @@ cryptodev_scheduler_create(const char *name,
 	}
 
 	for (i = 0; i < init_params->nb_slaves; i++) {
-		struct rte_cryptodev *slave_dev =
-				rte_cryptodev_pmd_get_named_dev(
-					init_params->slave_names[i]);
-
-		/* if the slave dev exists in the system, attach it */
-		if (slave_dev) {
-			int ret = rte_cryptodev_scheduler_slave_attach(
-				dev->data->dev_id,
-				slave_dev->data->dev_id);
-
-			if (ret < 0)
-				return ret;
-
-			CS_LOG_INFO("Scheduler %s attached slave %s\n",
-					dev->data->name,
-					init_params->slave_names[i]);
-
-			continue;
-		}
-
-		/* if the slave doesn't exist, store and attach later*/
 		sched_ctx->init_slave_names[sched_ctx->nb_init_slaves] =
 			rte_zmalloc_socket(
 				NULL,
-- 
2.7.4

             reply	other threads:[~2017-04-19 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 13:42 Fan Zhang [this message]
2017-04-19 16:04 ` [PATCH] crypto/scheduler: fix slave init attach De Lara Guarch, Pablo

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=1492609337-44733-1-git-send-email-roy.fan.zhang@intel.com \
    --to=roy.fan.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=stable@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.