Idle Loop Optimized
seebs writes "Every so often someone makes a joke about optimizing the idle loop, but this article actually does it. " It's about time too- that process has been eating up clock cycles for to long.
← Back to Stories (view on slashdot.org)
I run Gentoo.
finally.. a real post
Say, I'm curious, are you guys scripting this to post a new article every 5 minutes, or did you find some cheap outsourced labor to pound them out in real time?
This sig has been temporarily disconnected or is no longer in service
"Every so often someone makes a joke about optimizing the idle loop, but this article actually does it."
The article does what? Makes the joke, or optimizes the idle loop?
The webmaster in question said "yeah, I noticed a couple of extra visitors, but my TRS80-based web server coped just fine.".
Never email donotemail@WeAreSpammers.com
Show some restraint. It isn't necessary to publish EVERY LAST APRIL FOOLS JOKE found on the Internet. Give it a rest already!
-Charles
Learning HOW to think is more important than learning WHAT to think.
Today at work I was in a spectacularly smooth (and remarkably energy efficient) idle-loop.
Fortunately the loop was terminated automatically at 5pm.
------ The best brain training is now totally free : )
...have they implemented multicore support for greater speed and accuracy?
Um could you optimize the idle loop? Yeah... that would be great.
True, the article is partly an april fool's joke. What would you get by optimizing the idle loop? More cycles of the idle loop running in your idle time! But the 2nd half of the article discusses Altivec instructions. And seriously, there's useful information to be found there if you're writing Altivec code.
There are 10 kinds of people in the world - those that know binary, and those that don't.
I love this sort of thing. The basic idea is silly, but he manages to show some useful stuff and make some valid points while exploring it.
I remember in the 1980's there was a great article on how to add a GOSUB keyword to the FORTH language. The article evolved the code through four different versions, and each one showed something cool and useful about FORTH. Well, maybe not the last one:
: GOSUB ; IMMEDIATE
For those of you who don't grok FORTH, this defines a keyword called GOSUB that does nothing, and does it at compile time so it doesn't get compiled in either. (The article noted that GOSUB FOO is the same thing as just plain old FOO, since FORTH functions are always called as subroutines anyway.)
Around the same time, I saw an article on how to build your own 64KB memory: take a breadboard, and 65536 8-bit flip-flop chips, plus a 1:65536 multiplexer and a 65536:1 demultiplexer for address selection! The article helpfully calculated how many Watts of power it would take to drive all these chips (a LOT) but it didn't say where one might find a multiplexer or demultiplexer with over 65000 pins on it.
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely
I'm also worried about the lack of a decent defragmenter for the unused portions of my hard disk....
***You learn something Every day. And then you die.***