It would be awesome if we could have made it thinner -- the wing is there as the lowest-drag shape that we can put around the other components in the car -- suspension, steering, driver, etc. Its designed to be a lifting body because of the ground effect which would otherwise result in a negative lift. The cambered wing counters the negative lift generated by the ground effect.
This is what you need our research for. We can actually work out when the best time to change to a lower FSB/memory/IO/CPU frequency is with one nice tunable like you're used to... http://ertos.nicta.com.au/research/power
This is, of course, where you start to use a virtualised OS with a proven-secure hypervisor designed for exactly this job... Like OKL4.
Dave.
We did some work recently where we showed that in a lot of cases, running the CPU at a lower performance point actually resulted in more energy usage -- scaling down the CPU frequency means everything takes longer to run, which means that you get less time to spend in low-power idle modes. There are also a lot of other complexities with frequency scaling... Particularly on a platform like the Android where there would be multiple scalable frequencies, etc.
There's a whole lot of other problems with the slower-is-better approach... But check out the paper we've just published.
As a measure of QoS, I think this is quite cool work, but the way they translate this into frequency scaling seems broken.
Even bytes get lonely for a little bit.
