public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: linux-kernel@vger.kernel.org
Cc: John Richard Moser <nigelenki@comcast.net>
Subject: Re: Stealing ur megahurts (no, really)
Date: Fri, 19 May 2006 12:22:19 +0100	[thread overview]
Message-ID: <20060519112218.GE19673@gallifrey> (raw)
In-Reply-To: <446D61EE.4010900@comcast.net>

* John Richard Moser (nigelenki@comcast.net) wrote:

> Scrambling for an old machine is ridiculous.  Down-clocking makes sense
> because you can adjust to varied levels; but it's difficult and usually
> infeasible.  Pulling memory and mix and matching is not much better.

<...>

> This brings the idea of a cpumhz= parameter to adjust CPU clock rate.
> Obviously we can't do this directly, as convenient as this would be; but
> the idea warrants some thought, and some thought I gave it.  What I came
> up with was simple:  Adjust time slice length and place a delay between
> time slices so they're evenly spaced.

<...>

Hi John,
  While cpu downclocking helps a bit, it would be hopelessly inaccurate
for figuring out if your app would run fast enough on the given
ancient machine.  A lot else has happened to the world since the days
of the 200MHz CPU:
    * Faster memory
    * Larger caches
    * Faster PCI busses
    * Instruction set additions (various more levels of SSE etc)
    * Faster discs
    * Changes to the CPU architecture/implementation

Still, it would be interesting to see the difference in performance
of a downclocked modern processor and its 10 year old clock equivalent.

Dave

-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  parent reply	other threads:[~2006-05-19 11:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  6:13 Stealing ur megahurts (no, really) John Richard Moser
2006-05-19 10:10 ` Matti Aarnio
2006-05-19 15:40   ` Joel Jaeggli
2006-05-20 18:35     ` Antonio Vargas
2006-05-19 17:21   ` John Richard Moser
2006-05-19 11:02 ` Panagiotis Issaris
2006-05-19 15:06   ` Lexington Luthor
2006-05-19 17:22   ` John Richard Moser
2006-05-19 11:22 ` Dr. David Alan Gilbert [this message]
2006-05-19 11:43   ` linux-os (Dick Johnson)
2006-05-19 17:23   ` John Richard Moser
2006-05-19 17:37     ` Dr. David Alan Gilbert
2006-05-19 17:56       ` David Lang

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=20060519112218.GE19673@gallifrey \
    --to=linux@treblig.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@comcast.net \
    /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