Cache topology aware scheduling

[Danny Thomas]

Hi folks,

I was giving some thought to our adoption of Xen 4 coinciding with virtual
threads being available, and it occurred to me with an increasing number of
architectures clustering L3 and L2 caches between groups of cores on a die,
that virtual threads scheduling in user space could make them particularly
well suited to these architectures, if the scheduler were topology aware.

Have you given any thought to worker CPU affinity and/or locality to an
existing worker when a virtual thread is started by another? Would you
consider this something to be proved out by custom schedulers, or is this
enough of a trend to justify future investment in the default scheduler?

Cheers,
Danny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20240902/341e3acb/attachment.htm>