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 0B3C4A04B5; Wed, 16 Sep 2020 18:39:12 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C513F1C43E; Wed, 16 Sep 2020 18:39:10 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 8F1811C435 for ; Wed, 16 Sep 2020 18:39:09 +0200 (CEST) IronPort-SDR: f7P3sUNqzTL5wQfLN4CRQY8M52loIrSF3fsve1b1y8yEuhLpyrbVBQavNisVHEy2KvA1y1GPj8 1YB+VOeBlc0w== X-IronPort-AV: E=McAfee;i="6000,8403,9746"; a="223695935" X-IronPort-AV: E=Sophos;i="5.76,433,1592895600"; d="scan'208";a="223695935" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Sep 2020 09:39:07 -0700 IronPort-SDR: cYfiet4VsDek18MGTkefzfiufu5FKcyMlgvciSsjkV4XC8eA0+FnNNSvbbaxzACrNtrNGUndmx sw7lk2rHRgVA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.76,433,1592895600"; d="scan'208";a="307106577" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by orsmga006.jf.intel.com with ESMTP; 16 Sep 2020 09:39:05 -0700 Received: from sivswdev09.ir.intel.com (sivswdev09.ir.intel.com [10.237.217.48]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id 08GGd5hZ031650; Wed, 16 Sep 2020 17:39:05 +0100 Received: from sivswdev09.ir.intel.com (localhost [127.0.0.1]) by sivswdev09.ir.intel.com with ESMTP id 08GGd5MI007445; Wed, 16 Sep 2020 17:39:05 +0100 Received: (from lma25@localhost) by sivswdev09.ir.intel.com with LOCAL id 08GGd5NW007441; Wed, 16 Sep 2020 17:39:05 +0100 Date: Wed, 16 Sep 2020 17:39:05 +0100 From: "Liang, Ma" To: "Ananyev, Konstantin" Cc: "dev@dpdk.org" , "Hunt, David" , "Burakov, Anatoly" Message-ID: <20200916163905.GA5955@sivswdev09.ir.intel.com> References: <1597141666-20621-1-git-send-email-liang.j.ma@intel.com> <1599214740-3927-1-git-send-email-liang.j.ma@intel.com> <1599214740-3927-3-git-send-email-liang.j.ma@intel.com> <20200914210140.GE13240@sivswdev09.ir.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dpdk-dev] [PATCH v3 3/6] power: add simple power management API and callback 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" On 16 Sep 07:53, Ananyev, Konstantin wrote: Yes. we only has two gear. min or max. However, user still can customize their system max with power mgmt python script on Intel platform. > So rte_power_init(lcore) always raises lcore frequency to > max possible value? > > > > > > > > +rte_eth_remove_rx_callback(port_id, 0, > > > > + dev->cur_pwr_cb); > > > > +if (rte_power_exit(lcore_id)) > > > > +return -EINVAL; > > > > +break; > > > > +} > > > > + > > > > +dev->pwr_mgmt_state = RTE_ETH_DEV_POWER_MGMT_DISABLED; > > > > +dev->cur_pwr_cb = NULL; > > > > +dev->cb_mode = 0; > > > > + > > > > +return 0; > > > > +}