From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>,
"Varghese, Vipin" <vipin.varghese@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"nd@arm.com" <nd@arm.com>,
"honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples/service_cores: fix lcore count check
Date: Tue, 31 Aug 2021 16:09:10 +0000 [thread overview]
Message-ID: <BN0PR11MB5712CEFF9779471CEA7985A4D7CC9@BN0PR11MB5712.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210830080412.1548336-1-ruifeng.wang@arm.com>
> -----Original Message-----
> From: Ruifeng Wang <ruifeng.wang@arm.com>
> Sent: Monday, August 30, 2021 9:04 AM
> To: Van Haaren, Harry <harry.van.haaren@intel.com>; Varghese, Vipin
> <vipin.varghese@intel.com>
> Cc: dev@dpdk.org; thomas@monjalon.net; david.marchand@redhat.com;
> nd@arm.com; honnappa.nagarahalli@arm.com; Ruifeng Wang
> <ruifeng.wang@arm.com>; stable@dpdk.org
> Subject: [PATCH] examples/service_cores: fix lcore count check
>
> The example has various profiles to run services on specified
> number of lcores. Due to incorrect boundary condition, service
> can be dispatched to a core that does not exist. This puts main
> core into endless wait.
>
> Max available number of service cores is all detected lcores
> excluding main core.
>
> Fixes: 7f6ee6aee717 ("examples/service_cores: check cores before run")
> Cc: stable@dpdk.org
> Cc: vipin.varghese@intel.com
>
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
Change makes sense to me, this was introduced in Oct 2020
so a backport to 20.11 LTS makes sense I think.
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
next prev parent reply other threads:[~2021-08-31 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 8:04 Ruifeng Wang
2021-08-31 16:09 ` Van Haaren, Harry [this message]
2021-09-16 15:30 ` David Marchand
2021-09-16 15:36 ` 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=BN0PR11MB5712CEFF9779471CEA7985A4D7CC9@BN0PR11MB5712.namprd11.prod.outlook.com \
--to=harry.van.haaren@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=vipin.varghese@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).