From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1BA2745CE2; Mon, 11 Nov 2024 11:29:14 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DA03540E0C; Mon, 11 Nov 2024 11:29:13 +0100 (CET) Received: from fhigh-a3-smtp.messagingengine.com (fhigh-a3-smtp.messagingengine.com [103.168.172.154]) by mails.dpdk.org (Postfix) with ESMTP id 479014060C for ; Mon, 11 Nov 2024 11:29:12 +0100 (CET) Received: from phl-compute-10.internal (phl-compute-10.phl.internal [10.202.2.50]) by mailfhigh.phl.internal (Postfix) with ESMTP id CAA2F1140126; Mon, 11 Nov 2024 05:29:11 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-10.internal (MEProxy); Mon, 11 Nov 2024 05:29:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1731320951; x=1731407351; bh=TEplO4bM6jPa9jVfBnpdWQ3xFlqlBV1hangKlqfArrs=; b= szDtP+oKlB/8AoU3WrulnHGO4WASClbq+i5VJtx6Ed3tr7krNHF5gYWnEVa+oOjT 7bjeicUahekp4NdV60oPP4uYZEg30ef21c6wcaMRzQRdrnvOYx/66+diPh8mESNW Jx8Et//2a1Fi1clibPCMhywilxPs2y2dVZaggj3BBFuxEsnY4gltvtG+Q246dl5/ QI3Jw1723K3Wmb9urAu2ZVLiWtYpL79YxHZKvifuiA7vcKF5lVew/aB6B5j59i9/ jlpQ+I2IWpGx8+BkgrrP8VIitLh7MEq6lqRcU9ZpC+1g2TvVWjlzMqrAZheXd+s2 o+W/ckzKjvE0A4dJO9L9Bw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1731320951; x= 1731407351; bh=TEplO4bM6jPa9jVfBnpdWQ3xFlqlBV1hangKlqfArrs=; b=H 5peYsROw12nUR4qyU91mX12Icee55tvrqTY3MYvrVTXyqWDKez9trZumw2aMKFgf pM4ZTCLan5AcY3U2TSuqCBxJMMXJ3rQJ7Amt1W32NN3K8+Lh8MEs8/XTlc0DElCX 8nsWeQ6wFl4+cAceEPZD6wpUreap6aSvbieYTPexwzWwrBDddRAS+R3jGdi5S5EK UV8T9GQrSgYrDytfTLBFzKfeOkTDsWgVBUHToPNKlteRKfyR0WLcmBwQHgBbLTYC F6blqWlLhXCRjyAKoEH3mv5zX7rlP2S/HT89VGpJejrO+t6Nbq+yiXvmMKXaPfFJ cuz2z6EvrYMI8b0su1xGw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddruddvgdduiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenucfjughrpefhvfevufffkfgjfhgggfgtsehtufertddttdejnecu hfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlh honhdrnhgvtheqnecuggftrfgrthhtvghrnhepjedvieelieeghfegleekvdeludffjeef ueeuudeivdevgedufeevieeugeeftdeinecuffhomhgrihhnpehkvghrnhgvlhdrohhrgh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtpdhnsggprhgtphhtthhopeduvddpmhhouggvpe hsmhhtphhouhhtpdhrtghpthhtoheplhhihhhuihhsohhngheshhhurgifvghirdgtohhm pdhrtghpthhtohepuggvvhesughpughkrdhorhhgpdhrtghpthhtohepmhgssehsmhgrrh htshhhrghrvghshihsthgvmhhsrdgtohhmpdhrtghpthhtohepfhgvrhhruhhhrdihihhg ihhtsegrmhgurdgtohhmpdhrtghpthhtoheprghnrghtohhlhidrsghurhgrkhhovhesih hnthgvlhdrtghomhdprhgtphhtthhopegurghvihgurdhhuhhnthesihhnthgvlhdrtgho mhdprhgtphhtthhopehsihhvrghprhgrshgrugdrthhumhhmrghlrgesrghmugdrtghomh dprhgtphhtthhopehsthgvphhhvghnsehnvghtfihorhhkphhluhhmsggvrhdrohhrghdp rhgtphhtthhopehkohhnshhtrghnthhinhdrrghnrghnhigvvheshhhurgifvghirdgtoh hm X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 11 Nov 2024 05:29:09 -0500 (EST) From: Thomas Monjalon To: Huisong Li Cc: dev@dpdk.org, mb@smartsharesystems.com, ferruh.yigit@amd.com, anatoly.burakov@intel.com, david.hunt@intel.com, sivaprasad.tummala@amd.com, stephen@networkplumber.org, konstantin.ananyev@huawei.com, david.marchand@redhat.com, fengchengwen@huawei.com, liuyonglong@huawei.com Subject: Re: [PATCH v15 0/3] power: introduce PM QoS interface Date: Mon, 11 Nov 2024 11:29:08 +0100 Message-ID: <8000574.CvnuH1ECHv@thomas> In-Reply-To: <20241111022550.14113-1-lihuisong@huawei.com> References: <20240320105529.5626-1-lihuisong@huawei.com> <20241111022550.14113-1-lihuisong@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 11/11/2024 03:25, Huisong Li: > 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. > > 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. > > 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 > when wake up from idle state by setting strict resume latency (zero value). > > [1] https://www.kernel.org/doc/html/latest/admin-guide/abi-testing.html?highlight=pm_qos_resume_latency_us#abi-sys-devices-power-pm-qos-resume-latency-us Applied, thanks.