Re: [Xen-devel] [PATCH RFC 00/49] xen: add core scheduling support

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 29.03.19 at 16:08, <jgross@xxxxxxxx> wrote:
> Via boot parameter sched_granularity=core (or sched_granularity=socket)
> it is possible to change the scheduling granularity from thread (the
> default) to either whole cores or even sockets.

One further general question came to mind: How about also having
"sched-granularity=thread" (or "...=none") to retain current
behavior, at least to have an easy way to compare effects if
wanted? But perhaps also to allow to deal with potential resources
wasting configurations like having mostly VMs with e.g. an odd
number of vCPU-s.

The other question of course is whether the terms thread, core,
and socket are generic enough to be used in architecture
independent code. Even on x86 it already leaves out / unclear
where / how e.g. AMD's compute units would be classified. I
don't have any good suggestion for abstraction, so possibly
the terms used may want to become arch-specific.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel