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>,
	"Rybalchenko, Kirill" <kirill.rybalchenko@intel.com>,
	"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] crypto/scheduler: add multicore	scheduling mode
Date: Thu, 6 Jul 2017 08:32:24 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBD7064@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <9F7182E3F746AB4EA17801C148F3C60409EC00FD@IRSMSX101.ger.corp.intel.com>



> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Thursday, July 6, 2017 9:31 AM
> To: 'Zhang, Roy Fan' <roy.fan.zhang@intel.com>; Rybalchenko, Kirill
> <kirill.rybalchenko@intel.com>; Doherty, Declan
> <declan.doherty@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v3] crypto/scheduler: add multicore
> scheduling mode
> 
> 
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhang, Roy Fan
> > Sent: Thursday, July 6, 2017 2:42 AM
> > To: Rybalchenko, Kirill <kirill.rybalchenko@intel.com>; Doherty,
> > Declan <declan.doherty@intel.com>
> > Cc: dev@dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH v3] crypto/scheduler: add multicore
> > scheduling mode
> >
> > > -----Original Message-----
> > > From: Rybalchenko, Kirill
> > > Sent: Thursday, July 6, 2017 12:15 AM
> > > To: Zhang, Roy Fan <roy.fan.zhang@intel.com>; Doherty, Declan
> > > <declan.doherty@intel.com>
> > > Cc: dev@dpdk.org; Rybalchenko, Kirill <kirill.rybalchenko@intel.com>
> > > Subject: [PATCH v3] crypto/scheduler: add multicore scheduling mode
> > >
> > > Multi-core scheduling mode is a mode where scheduler distributes
> > > crypto operations in a round-robin base, between several core
> > > assigned as
> > workers.
> > >
> > > Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
> > > ---
> > > Changes in v3:
> > > - Rebased against dpdk-next-crypto
> > > - Fixed op status check in the reordering ring dequeuing
> > > - Modified size of the ring between scheduler and workers
> > > - Modified macro names as per Fan's comment
> > > - Changed type of variable from 'usigned int' to uint32_t
> >
> > Thanks a lot!
> >
> > Acked by: Fan Zhang <roy.fan.zhang@intel.com>
> 
> Applied to dpdk-next-crypto.
> Thanks,
> 
> Pablo

Forgot to say that I fixed a build error on gcc 32 bits and a minor issue in the documentation.

Pablo

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-28 20:08 [dpdk-dev] [PATCH] " Pablo de Lara
2017-05-31  7:48 ` De Lara Guarch, Pablo
2017-06-05  6:19 ` Zhang, Roy Fan
2017-06-30  9:51 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2017-07-05 16:14   ` [dpdk-dev] [PATCH v3] " Kirill Rybalchenko
2017-07-06  1:42     ` Zhang, Roy Fan
2017-07-06  8:30       ` De Lara Guarch, Pablo
2017-07-06  8:32       ` 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=E115CCD9D858EF4F90C690B0DCB4D8976CBD7064@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=kirill.rybalchenko@intel.com \
    --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).