From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id A554CA04A4; Tue, 26 May 2020 05:50:18 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 225781D976; Tue, 26 May 2020 05:50:18 +0200 (CEST) Received: from huawei.com (szxga07-in.huawei.com [45.249.212.35]) by dpdk.org (Postfix) with ESMTP id 219D81D971 for ; Tue, 26 May 2020 05:50:15 +0200 (CEST) Received: from DGGEMS407-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 65419DB1FF7B399D6E7B; Tue, 26 May 2020 11:50:14 +0800 (CST) Received: from [127.0.0.1] (10.67.103.119) by DGGEMS407-HUB.china.huawei.com (10.3.19.207) with Microsoft SMTP Server id 14.3.487.0; Tue, 26 May 2020 11:50:12 +0800 To: "Hunt, David" , David Marchand CC: Van Haaren Harry , dev , "Burakov, Anatoly" , "Pattan, Reshma" References: <3aeeb17b-66d0-cf87-df3a-0e2c313ba9ee@intel.com> From: oulijun Message-ID: Date: Tue, 26 May 2020 11:50:12 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <3aeeb17b-66d0-cf87-df3a-0e2c313ba9ee@intel.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.67.103.119] X-CFilter-Loop: Reflected Subject: Re: [dpdk-dev] =?utf-8?b?44CQQlVHIFJFUE9SVOOAkWwzZndkLXBvd2VyIGNhbiBu?= =?utf-8?q?ot_exit_by_ctrl+c?= X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi， I have update the code into 20.05-rc2. However， the l3fwd-power startup fail. [root@centos-C3 build]# l3fwd-power -w 0000:7d:00.1 -c 0xc000000 -n 4 -- -P -p 0x01 --config '(0,0,27)' --parse-ptype EAL: Detected 128 lcore(s) EAL: Detected 4 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'PA' EAL: No available hugepages reported in hugepages-2048kB EAL: No available hugepages reported in hugepages-32768kB EAL: No available hugepages reported in hugepages-64kB EAL: Probing VFIO support... EAL: VFIO support initialized EAL: using IOMMU type 1 (Type 1) EAL: Ignore mapping IO port bar(1) EAL: Ignore mapping IO port bar(3) EAL: Probe PCI driver: net_hns3 (19e5:a221) device: 0000:7d:00.1 (socket 0) No telemetry legacy support - No legacy callbacks, legacy socket not created Promiscuous mode selected soft parse-ptype is enabled POWER: Env isn't set yet! POWER: Attempting to initialise ACPI cpufreq power management... POWER: Power management governor of lcore 26 has been set to user space successfully POWER: File not opened POWER: Cannot get available frequencies of lcore 26 POWER: Attempting to initialise PSTAT power management... POWER: Power management governor of lcore 26 has been set to performance successfully POWER: Error opening '/dev/cpu/26/msr': No such file or directory POWER: Cannot init for setting frequency for lcore 26 POWER: Attempting to initialise VM power management... GUEST_CHANNEL: Opening channel '/dev/virtio-ports/virtio.serial.port.poweragent.26' for lcore 26 GUEST_CHANNEL: Unable to to connect to '/dev/virtio-ports/virtio.serial.port.poweragent.26' with error No such file or directory POWER: Unable to set Power Management Environment for lcore 26 POWER: Library initialization failed on core 26 EAL: Error - exiting with code: 1 Cause: init_power_library failed Thanks Lijun Ou 在 2020/5/22 17:02, Hunt, David 写道: > > 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 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. > > >