cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: cpufreq@lists.linux.org.uk, Bruno Ducrot <ducrot@poupinou.org>
Subject: RE: OnDemand governor vs. work queue
Date: Thu, 26 May 2005 07:48:27 +1000	[thread overview]
Message-ID: <1117057707.5076.23.camel@gaston> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6004D3529A@scsmsx403.amr.corp.intel.com>


> Agreed. For the larger latency transitions, ondemand governor should 
> use its own thread rather than keventd. Probably, it may make sense to 
> have separate threads for each CPU as well in that case (as otherwise 
> this thread will end up being moved around from one CPU to other. I will
> 
> look at this in a couple of weeks unless someone beats me to it and 
> sends the patch before that :).

A per-CPU thread could be a custom work queue (easy to implement form
current code) but also a resource waste. I don't think there is that
much of a problem having that thread moved around.

Ben.

  reply	other threads:[~2005-05-25 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 21:34 OnDemand governor vs. work queue Pallipadi, Venkatesh
2005-05-25 21:48 ` Benjamin Herrenschmidt [this message]
2005-05-25 22:04   ` Venkatesh Pallipadi
  -- strict thread matches above, loose matches on Subject: below --
2005-05-25  3:26 Benjamin Herrenschmidt
2005-05-25  9:59 ` Bruno Ducrot
2005-05-25 21:26   ` Benjamin Herrenschmidt

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=1117057707.5076.23.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=ducrot@poupinou.org \
    --cc=venkatesh.pallipadi@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