From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Rybalchenko, Kirill" <kirill.rybalchenko@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Rybalchenko, Kirill" <kirill.rybalchenko@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/crypto-perf: fix wait for lcores
Date: Thu, 6 Jul 2017 15:14:21 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBD76B4@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1497429873-117730-1-git-send-email-kirill.rybalchenko@intel.com>
> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Thursday, July 6, 2017 4:12 PM
> To: 'Kirill Rybalchenko' <kirill.rybalchenko@intel.com>; Doherty, Declan
> <declan.doherty@intel.com>
> Cc: dev@dpdk.org; Rybalchenko, Kirill <kirill.rybalchenko@intel.com>
> Subject: RE: [dpdk-dev] [PATCH] app/crypto-perf: fix wait for lcores
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kirill
> > Rybalchenko
> > Sent: Wednesday, June 14, 2017 9:45 AM
> > To: Doherty, Declan <declan.doherty@intel.com>
> > Cc: dev@dpdk.org; Rybalchenko, Kirill <kirill.rybalchenko@intel.com>;
> > stable@dpdk.org
> > Subject: [dpdk-dev] [PATCH] app/crypto-perf: fix wait for lcores
> >
> > After test is finished the main thread waits only for lcores where
> > runners were started, because it is responsibility of multicore
> > scheduler to stop and wait for workers lcores.
> >
> > Fixes: f8be1786b1b8 ("app/crypto-perf: introduce performance test
> > application")
> > CC: stable@dpdk.org
> >
> > Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
> > ---
>
> Since this is needed due to the new multi-core scheduler, I think it is not
> needed to be backported, as this is a new feature in this release.
> Will modify it.
>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2017-07-06 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 8:44 Kirill Rybalchenko
2017-07-06 15:11 ` De Lara Guarch, Pablo
2017-07-06 15:14 ` 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=E115CCD9D858EF4F90C690B0DCB4D8976CBD76B4@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 \
/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).