On 19/10/2017 13:49, David Gibson wrote: > Note that describing socket/core/thread tuples as arch independent (or > even machine independent) is.. debatable. I mean it's flexible enough > that most platforms can be fit to that scheme without too much > straining. But, there's no arch independent way of defining what each > level means in terms of its properties. > > So, for example, on spapr - being paravirt - there's no real > distinction between cores and sockets, how you divide them up is > completely arbitrary.
Same on x86, actually. It's _common_ that cores on the same socket share L3 cache and that a socket spans an integer number of NUMA nodes, but it doesn't have to be that way. QEMU currently enforces the former (if it tells the guest at all that there is an L3 cache), but not the latter. Paolo
signature.asc
Description: OpenPGP digital signature
