Re: [PATCH v2] perf bench: fix order of arguments to memcpy_alloc_mem

* Bruce Merry wrote: > This was causing the destination instead of the source to be filled. > As a result, the source was typically all mapped to one zero page, > and hence very cacheable. > > Signed-off-by: Bruce Merry > --- > tools/perf/bench/mem-memcpy.c | 4 ++-- > 1 file changed, 2

Re: [PATCH v2] perf bench: fix order of arguments to memcpy_alloc_mem

* Bruce Merry bme...@ska.ac.za wrote: This was causing the destination instead of the source to be filled. As a result, the source was typically all mapped to one zero page, and hence very cacheable. Signed-off-by: Bruce Merry bme...@ska.ac.za --- tools/perf/bench/mem-memcpy.c | 4 ++--

[PATCH v2] perf bench: fix order of arguments to memcpy_alloc_mem

This was causing the destination instead of the source to be filled. As a result, the source was typically all mapped to one zero page, and hence very cacheable. Signed-off-by: Bruce Merry --- tools/perf/bench/mem-memcpy.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH v2] perf bench: fix order of arguments to memcpy_alloc_mem

This was causing the destination instead of the source to be filled. As a result, the source was typically all mapped to one zero page, and hence very cacheable. Signed-off-by: Bruce Merry bme...@ska.ac.za --- tools/perf/bench/mem-memcpy.c | 4 ++-- 1 file changed, 2 insertions(+), 2