From: "Hunt, David" <david.hunt@intel.com>
To: oulijun <oulijun@huawei.com>, David Marchand <david.marchand@redhat.com>
Cc: Van Haaren Harry <harry.van.haaren@intel.com>, dev <dev@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"Pattan, Reshma" <reshma.pattan@intel.com>
Subject: Re: [dpdk-dev] 【BUG REPORT】l3fwd-power can not exit by ctrl+c
Date: Fri, 22 May 2020 10:02:33 +0100 [thread overview]
Message-ID: <3aeeb17b-66d0-cf87-df3a-0e2c313ba9ee@intel.com> (raw)
In-Reply-To: <b334130d-29cd-98f3-65f0-a9925d1c73cb@huawei.com>
On 22/5/2020 9:17 AM, oulijun wrote:
>
>
> 在 2020/5/20 15:22, David Marchand 写道:
>> Hello,
>>
>> On Wed, May 20, 2020 at 5:18 AM oulijun <oulijun@huawei.com> wrote:
>>> I am using 20.05-rc2 version to test based on HNS3 NIC
>>> hardware, and
>>> found that after starting l3fwd-power,
>>>
>>> using ctrl+c cannot force quit. But I revert the patch(33666b4 service:
>>> fix crash on exit) and it is ok.
>>
>> We had a fix in rc1 that is supposed to fix this.
>> https://git.dpdk.org/dpdk/commit?id=613ce6691c0d5ac0f99d7995f1e8e4ac86643882
>>
>>
>> Copying Anatoly and David H. too.
>>
> Hi, David Marchand
> I am only merged the patch(examples/l3fwd-power: implement proper
> shutdown) based on 20.05-rc0 and test. the bug is not resolved.
> Can you provide me with complete solution? I want to understand the
> cause of the whole problem
>
Hi Lijun,
The complete solution is to use a version with all of the fixes, as
Anatoly suggested previously. I have just checked out the latest tip of
the master branch, and l3fwd-power exits gracefully with a single CTRL-C:
...
Checking link statusdone
Port 0 Link Up - speed 100000 Mbps - full-duplex
L3FWD_POWER: entering main loop on lcore 27
L3FWD_POWER: -- lcoreid=27 portid=0 rxqueueid=0
L3FWD_POWER: lcore 26 has nothing to do
L3FWD_POWER: lcore 27 sleeps until interrupt triggers
*^C*POWER: Power management governor of lcore 26 has been set back to
successfully
POWER: Power management of lcore 26 has exited from 'performance' mode
and been set back to the original
POWER: Power management governor of lcore 27 has been set back to
successfully
POWER: Power management of lcore 27 has exited from 'performance' mode
and been set back to the original
#
Rgds,
Dave.
next prev parent reply other threads:[~2020-05-22 9:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 3:18 oulijun
2020-05-20 7:22 ` David Marchand
2020-05-20 8:41 ` oulijun
2020-05-20 8:49 ` David Marchand
2020-05-20 11:37 ` Burakov, Anatoly
2020-05-22 8:17 ` oulijun
2020-05-22 9:00 ` Burakov, Anatoly
2020-05-22 9:02 ` Hunt, David [this message]
2020-05-26 3:50 ` oulijun
2020-05-26 8:36 ` Hunt, David
2020-05-26 9:11 ` oulijun
2020-05-27 6:10 ` oulijun
2020-05-27 8:21 ` Hunt, David
2020-05-26 9:24 ` Burakov, Anatoly
2020-05-27 6:04 ` oulijun
2020-05-27 8:57 ` Burakov, Anatoly
2020-05-20 9:45 ` Burakov, Anatoly
2020-05-21 1:26 ` oulijun
2020-05-21 10:46 ` Burakov, Anatoly
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=3aeeb17b-66d0-cf87-df3a-0e2c313ba9ee@intel.com \
--to=david.hunt@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=oulijun@huawei.com \
--cc=reshma.pattan@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).