[ovirt-devel] Clarify NUMA feature and CPU pinning

[Liao, Chuan (Jason Liao, HPservers-Core-OE-PSC)]

Hi Gilad & Einav

Thanks for sharing your ideas about NUMA feature and CPU pinning. It makes easier for users to understand.

And something I want to clarify:

1.      NUMA tuning feature and CPU pinning feature are individually in libvirt ( ovirt backend ).

2.      User could configure VM CPU pining ( NUMA not included ) separately.

3.      When configuring NUMA feature, user should configure VM NUMA tuning ( pin to host NUMA node & tuning mode ) and VM CPU pinning ( NUMA included ), otherwise VM will have low performance.

4.      Single virtual NUMA node could pin to multiply host NUMA nodes.

5.      Multiply virtual NUMA nodes could pin to single host NUMA node.

6.      NUMA tuning mode have default value 'strict', and could change to 'prefer', 'interleave'

Our proposal:
OVirt 3.5

1.      Keep current UX design, add NUMA tuning mode select box in VM dialog.

2.      Keep current BE model, query and action command.

3.      Consider the low performance scene ( user did not configure VM CPU pinning )

When VdsBroker check the CPU pinning text is empty, then generate the right CPU pinning text from virtual NUMA nodes ( pin to host NUMA nodes )

The next version

1.      Remove current CPU pinning text feature.

2.      Consider the NUMA node inside CPU pinning design. ( Should consider the individually CPU pining design not includes NUMA )

3.      Add related CPU pinning BE model, query and action command.

4.      Turn off VdsBroker generate function.

Do you agree ?

Best Regards,
Jason Liao

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20140411/5a76d7c6/attachment-0001.html>