From: "Eduard Giménez" <edu@badopi.org>
To: linux-pm@lists.osdl.org
Subject: Request for suggestions
Date: Thu, 28 Sep 2006 00:23:23 +0200 [thread overview]
Message-ID: <200609280023.23798.edu@badopi.org> (raw)
Hello,
As a Final Project to the Diploma in Computer Systems I'm researching ways to improve
power savings consumption on idle systems. We're aiming to improve the usage of
low power states on the processor (Px and Cx states on ACPI jargon) mainly on x86
computers, but when possible all improvements will be done architecture independent.
We have been thinking of direct improvements (p.e. better algorithms for CPU
frequency/state management) and indirect improvements, things like dynticks
or trying the reduce the USB poll rate.
Currently I'm writting a list of proposals, and as far as I want to do some
useful work I ask you if there is any new feature or improvement that would be welcomed.
Any suggestion will be added to the proposals list to be reviewed.
Thank you in advance!
--
edu
next reply other threads:[~2006-09-27 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 22:23 Eduard Giménez [this message]
2006-09-28 8:19 ` Request for suggestions Pavel Machek
2006-10-03 22:24 ` Wes Felter
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=200609280023.23798.edu@badopi.org \
--to=edu@badopi.org \
--cc=linux-pm@lists.osdl.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