Li, Aubrey wrote:
Some of properties was implemented about a decade ago, if it's not easy
to figure them out and move to SMF in a short time, I think keeping some
in SMF and others in power.conf at the same time is probably not a bad idea.
That would give us a chance to know how the new SMF PM setting looks like and
also give who is interested in this migration an opportunity to do the help.
Autoshutdown really serves two purposes IMHO:
1. I may know that I want my desktop to go into low power mode, sleep,
or shutdown at 7pm or midnight every day, regardless of load such as
whether flash/firefox is using too much CPU. (I might also want Firefox
excluded from normal idleness considerations, but that's another story).
2. I suspect that part of the reason "autoshutdown" is in power.conf in
the first place is because, before UltraSPARC-III, none of the
UltraSPARC-I/II CPUs could do frequency scaling, and therefore the only
way for Sun to implement the original EnergyStar certification before
2000 was to use autoshutdown.
The fact is that most customers probably never used autoshutdown (or
autosleep), and those that did probably did this based on schedule
rather than idleness. But there was a marketing need for EnergyStar on
the box.
Once UltraSPARC-III (and -IIe shipped - I don't know about -IIi) in
2000, then frequency scaling became an arguably better option. And of
course today, both AMD and Intel CPUs have much more extensive
frequency/voltage and C-state scaling as well as other system-level
power savings.
I would suspect, in this regard, that any type of autoshutdown is more
likely to be useful based on schedule rather than pure load, potentially
linked to "wake up for cron jobs" or similar.
Hugh.
_______________________________________________
pm-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pm-discuss
