DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] crypto/scheduler: remove session backup and recover
Date: Thu, 6 Jul 2017 08:43:18 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBD70AF@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20170526012443.13001-1-roy.fan.zhang@intel.com>



> -----Original Message-----
> From: Zhang, Roy Fan
> Sent: Friday, May 26, 2017 2:25 AM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: [PATCH] crypto/scheduler: remove session backup and recover
> 
> This patch removes the unnecssary session backup and recover steps in the
> round-robin and fail-over modes of cryptodev scheduler PMD. Originally,
> the scheduler blindly enqueues to the slaves regardless of their available
> queue rooms, and recovers the sessions once failed. This patch predicts the
> number of crypto ops the slave can be enqueued by checking its inflight ops
> and thus removed the session backup and recovery steps.
> 
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
>  drivers/crypto/scheduler/scheduler_failover.c   | 33 +++++++++---------------
> -
>  drivers/crypto/scheduler/scheduler_roundrobin.c | 33 ++++++++++----------
> -----
>  2 files changed, 25 insertions(+), 41 deletions(-)

Hi Fan,

Thanks for the patch. I did not apply this patch so far because there was some work
ongoing about the crypto sessions. Since this work is going to be integrated for RC1,
this patch is not needed anymore.

Thanks,
Pablo

      reply	other threads:[~2017-07-06  8:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26  1:24 Fan Zhang
2017-07-06  8:43 ` De Lara Guarch, Pablo [this message]

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=E115CCD9D858EF4F90C690B0DCB4D8976CBD70AF@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@dpdk.org \
    --cc=roy.fan.zhang@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).