From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Youquan Song <youquan.song@linux.intel.com>
Cc: <linux-pm@vger.kernel.org>, <youquan.song@intel.com>
Subject: Re: [PATCH] PM/QoS: resume latency 0 should be not latency allowed
Date: Wed, 10 Nov 2021 20:24:12 +0100 [thread overview]
Message-ID: <2d01125c-facd-6db6-23d3-b0b1b608c4e8@intel.com> (raw)
In-Reply-To: <20211110105833.GA30301@linux-youquan.bj.intel.com>
On 11/10/2021 11:58 AM, Youquan Song wrote:
>> But do you really need to make these changes? What problem is there with using the interface as currently documented, ie. writing "n/a" to it to get "no latency at all"?
> I think so. "0" is "latency is not allowed", but "n/a" is "no latency".
>
Actually, "0" means "I don't care" and "n/a" means "no latency" which
means latency tolerance == 0.
next prev parent reply other threads:[~2021-11-10 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 11:36 [PATCH] PM/QoS: resume latency 0 should be not latency allowed Youquan Song
2021-11-05 15:50 ` Rafael J. Wysocki
[not found] ` <BYAPR11MB3205164D85635F784AFA4C429C939@BYAPR11MB3205.namprd11.prod.outlook.com>
[not found] ` <20211110105833.GA30301@linux-youquan.bj.intel.com>
2021-11-10 19:24 ` Rafael J. Wysocki [this message]
2021-11-11 4:28 ` Youquan Song
2021-11-11 17:07 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d01125c-facd-6db6-23d3-b0b1b608c4e8@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=youquan.song@intel.com \
--cc=youquan.song@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox