From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: cpufreq@lists.linux.org.uk
Subject: OnDemand governor vs. work queue
Date: Wed, 25 May 2005 13:26:40 +1000 [thread overview]
Message-ID: <1116991600.6395.71.camel@gaston> (raw)
Hi !
From what I've seen, the OnDemand governor works using a timer/workqueue
pair.
That annoys me a bit as the setup I have on PowerMacs can take several
ms to transition (due to voltage transition mostly). I don't like the
idea of hogging keventd that long.
Wouldn't it make sense, especially for setups where transition latency
is high (by high, I mean significant compared to HZ for example), to
actually spawn a kthread and do the sampling & switching from there ?
Regard,
Ben.
next reply other threads:[~2005-05-25 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 3:26 Benjamin Herrenschmidt [this message]
2005-05-25 9:59 ` OnDemand governor vs. work queue Bruno Ducrot
2005-05-25 21:26 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2005-05-25 21:34 Pallipadi, Venkatesh
2005-05-25 21:48 ` Benjamin Herrenschmidt
2005-05-25 22:04 ` Venkatesh Pallipadi
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=1116991600.6395.71.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=cpufreq@lists.linux.org.uk \
/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