All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "Gross, Mark" <mark.gross@intel.com>
Cc: linux-pm@osdl.org, PMWG@LIST.CELINUXFORUM.ORG,
	mli_tech@groups.osdl.org, celinux-dev@tree.celinuxforum.org
Subject: Re: CE Linux Forum PM Requierments WiKi is available for review and comment.
Date: Wed, 22 Mar 2006 10:41:27 +0100	[thread overview]
Message-ID: <20060322094127.GH14075@elf.ucw.cz> (raw)
In-Reply-To: <5389061B65D50446B1783B97DFDB392D2042B3@orsmsx411.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]

Hi!

> >Hmm, okay, yes, that would be useful for machines that can't do
> >throttling in hardware.
> 
> Even platforms that can throttle in hardware, it could make sense for to
> throttle the OS.  

Well, certainly. If you want to throttle to 1% and hardware can only
throttle to 30%, you need to do it in software.

> I think a person may want to throttle what work a laptop is doing as a
> function of being tethered or remaining battery life.  If all you want
> to do is finish those last few edits to a file before your battery cuts
> you off for the rest of a long flight, you will be very willing to shut
> down most (all?) processing that's not related to what you are editing.
> Cron jobs, automatic spell checking, sound subsystems, screen savers,
> pretty much anything not related to your editing will pull down your
> battery.  Most of these can be shut down from user mode, some things may
> be easier to implement robustly with some kernel support.  

That will be userland parts, I'd say.

> One idea is to extend the SCHED_BATCH idea to know about power state to
> avoid running some things when un-tethered or under low battery
> conditions.

Idle thread with realtime priority could do parts of what you want.

> >> >Thanks, Sharp!
> >>
> >> Who the heck is Sharp, and why do you always thank him?
> >
> >That's a signature... Sharp is Japaneese firm, maybe you've heard
> >about them :-). Send me handheld computer, and that line becomes
> >"Thanks, Intel" ;-).
> 
> Oh! Ok, that makes sense.  BTW careful what you wish for....

Well, I currently have collie (sharp sl-5500) for hacking, and spitz
(c-3000) for normal use. I would not mind hacking on something not as
obsolete.
								Pavel
-- 
Picture of sleeping (Linux) penguin wanted...

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2006-03-22  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 23:49 CE Linux Forum PM Requierments WiKi is available for review and comment Gross, Mark
2006-03-22  9:41 ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-21 20:09 Gross, Mark
2006-03-21 20:36 ` Pavel Machek
2006-03-16 16:01 Gross, Mark
2006-03-19 19:22 ` Pavel Machek

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=20060322094127.GH14075@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=PMWG@LIST.CELINUXFORUM.ORG \
    --cc=celinux-dev@tree.celinuxforum.org \
    --cc=linux-pm@osdl.org \
    --cc=mark.gross@intel.com \
    --cc=mli_tech@groups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.