If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I don't know a whole lot about the big.LITTLE architecture, but I think it'd be really cool if Linux were designed so kernel tasks, X, the compositor, pulseaudio, bluetooth, and other background processes were all dumped to the A7 cores and then use the A15 cores for all front-end userspace applications.

I never understood why big.LITTLE needs 4 A7 cores. I think 1 or 2 is sufficient for the purposes they're supposed to fulfill, even in phones.

I don't know a whole lot about the big.LITTLE architecture, but I think it'd be really cool if Linux were designed so kernel tasks, X, the compositor, pulseaudio, bluetooth, and other background processes were all dumped to the A7 cores and then use the A15 cores for all front-end userspace applications.

That's what will happen, assuming you're using the "full 8 cores", not the "big.little" scheduler choice. The less-cpu-using apps will be migrated to the lower cores, the more-cpu-using to the big cores.

And if you need to force a specific process somewhere, that's one command away.

That's what will happen, assuming you're using the "full 8 cores", not the "big.little" scheduler choice. The less-cpu-using apps will be migrated to the lower cores, the more-cpu-using to the big cores.

And if you need to force a specific process somewhere, that's one command away.