On 13/05/13 14:46, Hu Tao wrote:
On Thu, May 09, 2013 at 06:22:17PM +0800, Osier Yang wrote:
When the numatune memory mode is not "strict", the cpuset.mems
inherits the parent's setting, which causes problem like:
% virsh dumpxml rhel6_local | grep interleave -2
2
% cat /p
On Thu, May 09, 2013 at 06:22:17PM +0800, Osier Yang wrote:
> When the numatune memory mode is not "strict", the cpuset.mems
> inherits the parent's setting, which causes problem like:
>
> % virsh dumpxml rhel6_local | grep interleave -2
> 2
>
>
>
>
>
> % cat /proc/3713/status | g
On 09/05/13 18:23, Osier Yang wrote:
Missed the address, :\
[cC Hu Tao]
On 09/05/13 18:22, Osier Yang wrote:
When the numatune memory mode is not "strict", the cpuset.mems
inherits the parent's setting, which causes problem like:
% virsh dumpxml rhel6_local | grep interleave -2
2
When the numatune memory mode is not "strict", the cpuset.mems
inherits the parent's setting, which causes problem like:
% virsh dumpxml rhel6_local | grep interleave -2
2
% cat /proc/3713/status | grep Mems_allowed_list
Mems_allowed_list:0-3
% virsh numatune rhel6_local
[cC Hu Tao]
On 09/05/13 18:22, Osier Yang wrote:
When the numatune memory mode is not "strict", the cpuset.mems
inherits the parent's setting, which causes problem like:
% virsh dumpxml rhel6_local | grep interleave -2
2
% cat /proc/3713/status | grep Mems_allowed_list
