From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id F409945492;
	Wed, 19 Jun 2024 08:59:33 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id DA2364026E;
	Wed, 19 Jun 2024 08:59:33 +0200 (CEST)
Received: from dkmailrelay1.smartsharesystems.com
 (smartserver.smartsharesystems.com [77.243.40.215])
 by mails.dpdk.org (Postfix) with ESMTP id 710484021D
 for <dev@dpdk.org>; Wed, 19 Jun 2024 08:59:32 +0200 (CEST)
Received: from smartserver.smartsharesystems.com
 (smartserver.smartsharesys.local [192.168.4.10])
 by dkmailrelay1.smartsharesystems.com (Postfix) with ESMTP id 465E620778;
 Wed, 19 Jun 2024 08:59:32 +0200 (CEST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [PATCH v3 0/2] power: introduce PM QoS interface
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Jun 2024 08:59:31 +0200
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F53B@smartserver.smartshare.dk>
In-Reply-To: <20240619063144.20733-1-lihuisong@huawei.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PATCH v3 0/2] power: introduce PM QoS interface
Thread-Index: AdrCE5L8IjNlEyzYT/2w2fEdRwy52QAAoDGA
References: <20240320105529.5626-1-lihuisong@huawei.com>
 <20240619063144.20733-1-lihuisong@huawei.com>
From: =?iso-8859-1?Q?Morten_Br=F8rup?= <mb@smartsharesystems.com>
To: "Huisong Li" <lihuisong@huawei.com>,
	<dev@dpdk.org>
Cc: <thomas@monjalon.net>, <ferruh.yigit@amd.com>, <anatoly.burakov@intel.com>,
 <david.hunt@intel.com>, <sivaprasad.tummala@amd.com>,
 <david.marchand@redhat.com>, <liuyonglong@huawei.com>
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

> From: Huisong Li [mailto:lihuisong@huawei.com]
> Sent: Wednesday, 19 June 2024 08.32
>=20
> The deeper the idle state, the lower the power consumption, but the =
longer
> the resume time. Some service are delay sensitive and very except the =
low
> resume time, like interrupt packet receiving mode.
>=20
> And the "/sys/devices/system/cpu/cpuX/power/pm_qos_resume_latency_us" =
sysfs
> interface is used to set and get the resume latency limit on the cpuX =
for
> userspace. Please see the description in kernel document[1].
> Each cpuidle governor in Linux select which idle state to enter based =
on
> this CPU resume latency in their idle task.
>=20
> The per-CPU PM QoS API can be used to control this CPU's idle state
> selection and limit just enter the shallowest idle state to low the =
delay
> after sleep by setting strict resume latency (zero value).
>=20
> [1] https://www.kernel.org/doc/html/latest/admin-guide/abi-
> =
testing.html?highlight=3Dpm_qos_resume_latency_us#abi-sys-devices-power-p=
m-qos-
> resume-latency-us
>=20
> ---
>  v3:
>   - add RTE_POWER_xxx prefix for some macro in header
>   - add the check for lcore_id with rte_lcore_is_enabled
>  v2:
>   - use PM QoS on CPU wide to replace the one on system wide

Series-acked-by: Morten Br=F8rup <mb@smartsharesystems.com>