From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Creating scheduler
Date: Wed, 06 Feb 2013 15:35:50 -0500 [thread overview]
Message-ID: <18379.1360182950@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 06 Feb 2013 20:40:47 +0100." <20130206194047.GA3133@debian.debian>
On Wed, 06 Feb 2013 20:40:47 +0100, Jonathan Neusch?fer said:
> I'm sorry to ask, but don't you rather mean watts than watts per second?
There may indeed be a second order time component involved - for instance, a
cooling system that can handle 10 watts continuously, 20 watts for up to 30
seconds, or 40 watts for 10 seconds max. And of course, "40 watts steady for 10
seconds" is different from "averaging 40 watts but bouncing between 30 and 50
watts for 10 seconds" etc etc..
And of course, there's usually a per-system limit, and per-chip limits, and
your power/cooling budget constraints may force you to go for a higher value
on one to make the budget for the other (burn an extra 0.5 watts in chip A
in order to get Chip B under 0.87 watts type stuff)....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130206/831eb7f2/attachment.bin
next prev parent reply other threads:[~2013-02-06 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 17:49 Creating scheduler jeshkumar555
2013-02-06 18:16 ` Valdis.Kletnieks at vt.edu
2013-02-06 19:40 ` Jonathan Neuschäfer
2013-02-06 20:35 ` Valdis.Kletnieks at vt.edu [this message]
2013-02-07 4:08 ` Peter Teoh
-- strict thread matches above, loose matches on Subject: below --
2013-02-07 4:45 jeshkumar555
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=18379.1360182950@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).