RE: [libvirt][PATCH v2 0/3] introduce 'restrictive' mode in numatune

2021-01-05 Thread Zhong, Luyao
Thanks Daniel, I forgot it.  Regards, Luyao -Original Message- From: Daniel Henrique Barboza Sent: Tuesday, January 5, 2021 8:29 PM To: Zhong, Luyao ; libvir-list@redhat.com Subject: Re: [libvirt][PATCH v2 0/3] introduce 'restrictive' mode in numatune Luyao, I failed to realize

Re: [libvirt][PATCH v2 0/3] introduce 'restrictive' mode in numatune

2021-01-05 Thread Daniel Henrique Barboza
Luyao, I failed to realize, back in the v1 version of your patches, that you didn't sign them with a "Signed-off-by" tag. This is required to assert that you agree with the terms of the Developer Certificate of Origin, described here: https://developercertificate.org/ This is described in

[libvirt][PATCH v2 0/3] introduce 'restrictive' mode in numatune

2021-01-03 Thread Luyao Zhong
Before this patch set, numatune only has three memory modes: static, interleave and prefered. These memory policies are ultimately set by mbind() system call. Memory policy could be 'hard coded' into the kernel, but none of above policies fit our requirment under this case. mbind() support