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 B0440A0093; Thu, 21 May 2020 03:26:54 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EE2181C22E; Thu, 21 May 2020 03:26:53 +0200 (CEST) Received: from huawei.com (szxga04-in.huawei.com [45.249.212.190]) by dpdk.org (Postfix) with ESMTP id F1B891C22A for ; Thu, 21 May 2020 03:26:51 +0200 (CEST) Received: from DGGEMS413-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 69C10102D329A6D8A3E6; Thu, 21 May 2020 09:26:49 +0800 (CST) Received: from [127.0.0.1] (10.67.103.119) by DGGEMS413-HUB.china.huawei.com (10.3.19.213) with Microsoft SMTP Server id 14.3.487.0; Thu, 21 May 2020 09:26:49 +0800 To: "Burakov, Anatoly" , , CC: References: From: oulijun Message-ID: Date: Thu, 21 May 2020 09:26:49 +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: 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" 在 2020/5/20 17:45, Burakov, Anatoly 写道: > On 20-May-20 4:18 AM, oulijun wrote: >> Hi, David Marchand && guys >> >> 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. >> >> the log as follows: >> >> Initializing rx queues on lcore 26 ... >> Initializing rx queues on lcore 27 ... rxq=0,0,0 Port 0: softly parse >> packet type info >> >> >> Checking link status...............0000:7d:00.1 >> hns3_update_link_status(): Link status change to up! >> done >> Port 0 Link Up - speed 25000 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 >> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0 >> L3FWD_POWER: lcore 27 sleeps until interrupt triggers >> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0 >> L3FWD_POWER: lcore 27 sleeps until interrupt triggers >> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0 >> L3FWD_POWER: lcore 27 sleeps until interrupt triggers >> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0 >> L3FWD_POWER: lcore 27 sleeps until interrupt triggers >> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0 >> L3FWD_POWER: lcore 27 sleeps until interrupt triggers >> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0 >> L3FWD_POWER: lcore 27 sleeps until interrupt triggers >> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0 >> L3FWD_POWER: lcore 27 sleeps until interrupt triggers >> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0 >> L3FWD_POWER: lcore 27 sleeps until interrupt triggers >> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0 >> L3FWD_POWER: lcore 27 sleeps until interrupt triggers >> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0 >> L3FWD_POWER: lcore 27 sleeps until interrupt triggers >> L3FWD_POWER: lcore 27 is waked up from rx interrupt on port 0 queue 0 >> L3FWD_POWER: lcore 27 sleeps until interrupt triggers >> ^CPOWER: Power management governor of lcore 26 has been set back to >> successfully >> POWER: Power management of lcore 26 has exited from 'userspace' 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 'userspace' mode >> and been set back to the original >> 0000:7d:00.1 hns3_dev_close(): Close port 0 finished >> User forced exit > > The "user forced exit" string is from before the patches were applied. > You are obviously not using the rc2 version. Please pull down the latest > l3fwd-power code and retest. > sorry， our version is 20.05-rc0 >> [root@centos-C3 build]# >> >> Thanks >> >> Lijun Ou >> >> >> >> >> >> > >