From: Radu Nicolau <radu.nicolau@intel.com>
To: "Hunt, David" <david.hunt@intel.com>, dev@dpdk.org
Cc: lei.a.yao@intel.com, pablo.de.lara.guarch@intel.com
Subject: Re: [dpdk-dev] [PATCH v3] examples/l3fw-power: do not exit on power lib init failure
Date: Tue, 7 Aug 2018 17:50:20 +0100 [thread overview]
Message-ID: <e2e2504f-59f3-ad0d-2caf-c89991eabe61@intel.com> (raw)
In-Reply-To: <1a6d5cf7-0a8a-be5d-6147-373b94599535@intel.com>
On 8/7/2018 4:45 PM, Hunt, David wrote:
> On 7/8/2018 2:24 PM, Radu Nicolau wrote:
>> Do not exit the application if power library fails to initialize
>> or high performance cores configuration cannot be used - this was the
>> behavior of the application before the patch that added the high/regular
>> performance option and also this is the normally expected behavior, the
>> application can be used with no power options, i.e. test framework.
>>
>> Fixes: f88e7c175a68 ("examples/l3fwd-power: add high/regular perf
>> cores options")
>>
>> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
>> ---
>
> Acked-by: David Hunt <david.hunt@intel.com>
After further internal discussions we will revise the behavior of the
app when exiting due to failed init.
We will try to get a new patch for 18.11.
prev parent reply other threads:[~2018-08-07 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 13:49 [dpdk-dev] [PATCH] " Radu Nicolau
2018-07-26 17:39 ` De Lara Guarch, Pablo
2018-07-27 9:56 ` Radu Nicolau
2018-07-27 9:53 ` [dpdk-dev] [PATCH v2] " Radu Nicolau
2018-08-05 20:26 ` Thomas Monjalon
2018-08-07 13:16 ` Hunt, David
2018-08-07 13:24 ` [dpdk-dev] [PATCH v3] " Radu Nicolau
2018-08-07 15:45 ` Hunt, David
2018-08-07 16:50 ` Radu Nicolau [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=e2e2504f-59f3-ad0d-2caf-c89991eabe61@intel.com \
--to=radu.nicolau@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=lei.a.yao@intel.com \
--cc=pablo.de.lara.guarch@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).