| commit | 288d3322022d6ad646407f3ca6f1a6a746565b9a | |
| author | Michael S. Tsirkin <mst@redhat.com> | |
| Wed, 13 Aug 2014 11:50:24 +0000 (13 13:50 +0200) | ||
| committer | Michael S. Tsirkin <mst@redhat.com> | |
| Wed, 20 Aug 2014 19:15:56 +0000 (20 21:15 +0200) | ||
| tree | 8a43bc27a61b496441418ceb88f8d800f3be51e0 | treesnapshot (tar.gz zip) |
| parent | 2656eb7c599e306b95bad82b1372fc49ba3088f6 | commitdiff |
hostmem: set MPOL_MF_MOVE
When memory is allocated on a wrong node, MPOL_MF_STRICT
doesn't move it - it just fails the allocation.
A simple way to reproduce the failure is with mlock=on
realtime feature.
The code comment actually says: "ensure policy won't be ignored"
so setting MPOL_MF_MOVE seems like a better way to do this.
Cc: qemu-stable@nongnu.org
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
When memory is allocated on a wrong node, MPOL_MF_STRICT
doesn't move it - it just fails the allocation.
A simple way to reproduce the failure is with mlock=on
realtime feature.
The code comment actually says: "ensure policy won't be ignored"
so setting MPOL_MF_MOVE seems like a better way to do this.
Cc: qemu-stable@nongnu.org
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
| backends/hostmem.c | diffblobblamehistory |