public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: markgross@thegnar.org
Cc: Linux PM <linux-pm@lists.linux-foundation.org>
Subject: Re: [RFC] pm_qos: reimplement using plists
Date: Sun, 06 Jun 2010 22:41:10 -0400	[thread overview]
Message-ID: <1275878470.7227.557.camel@mulgrave.site> (raw)
In-Reply-To: <20100606210553.GB8610@gvim.org>

On Sun, 2010-06-06 at 14:05 -0700, mark gross wrote:
> what is the scaling charactoristics of plist's for things that have a
> large dynamic range and a significant utilization of it?  (say 16 bits
> of it.  Which is very unlikely to ever happen)

well O(1) as the document says ... actually it's O(n) where n is the
number of different values in the list.  However, it's always better
than the manual search of a single list that pm_qos currently does. 

> I think in practice this will not be an issue as most users only ever
> call the pm_qos API with 2 values (at least kernel users of the API) 

Well, it's better in every case, not just the low range cases.

> I've only had a quick look so far but it looks really good to me.

Thanks.

James

  reply	other threads:[~2010-06-07  2:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05 17:58 [RFC] pm_qos: reimplement using plists James Bottomley
2010-06-05 18:17 ` Rafael J. Wysocki
2010-06-05 18:19   ` James Bottomley
2010-06-06 21:05 ` mark gross
2010-06-07  2:41   ` James Bottomley [this message]
2010-06-06 21:39 ` mark gross
2010-06-07  3:05   ` James Bottomley
2010-06-09  6:38     ` Florian Mickler
2010-06-09 14:03       ` James Bottomley
2010-06-08 13:31   ` mark gross
2010-06-08 15:52     ` James Bottomley
2010-06-09  2:42       ` mark gross
2010-06-09 14:03         ` James Bottomley

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=1275878470.7227.557.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=markgross@thegnar.org \
    /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