ARM Big.LITTLE processing addresses one of today's most significant challenges: extending consumers' always on, always connected mobile experience with both improved performance AND longer battery life. It achieves this by grouping a ‘big’ multicore processor with a ‘LITTLE’ multicore processor and seamlessly selecting the right processor for the right task, based on performance requirements. Importantly, this dynamic selection is transparent to the application software or middleware running on the processors.
This paper outline the different implementation techniques and the variety of use-models that enable big.LITTLE processing to provide the opportunity to raise performance and extend battery life in the next generation of mobile platforms.
Two questions:
(1) Could the big.little system use the big system libs ?
(2) Is there another tool chain to re-compile the code for the big.little system ?
for example:
We have mp3 decoder libs used in big system before.
(1) For big.little system, could it be used directly ?
(2) Is it necessary to use another tool chain to re-compile the mp3 source code ?