Scaling noise
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · Steven Cole
The question which will continue to be important in the next kernel series is: How to best accommodate the future many-CPU machines without sacrificing performance on the low-end? The change is that the 'many' in the above may start to double every few years.
Some candidate answers to this have been discussed before, such as cache-coherent clusters. I just hope this gets worked out before the hardware ships.
RT frame works are running single kernel under some kind of RT OS.
It should be possible to develop framework to run several Linuces
under single instance of another OS (or Linux itself). And every instance of slave Linux whould be told which resources it is responsible for.
You can /partition/ memory, you can say that given instance of kernel
should use e.g. only CPUs from Nth to N+Mth.
But some resources - like IDE controllers, GPUs, NICs - are not that
easy to share. Actually most of the resources are not trivial to share.
And I'm not sure what will turns out to be easier: write very
scaleable kernel or make kernel been able to share efficiently resources with others.
P.S. My personal belief - that SMP is never going to become comodity. EPIC/VLIW - probably. Not SMP/AMP.