mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@infradead.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.jf.intel.com>,
	h.mitake@gmail.com, kirill.shutemov@linux.jf.intel.com
Subject: RE: [PATCH] perf, tools, bench: Fix memcpy benchmark for large sizes
Date: Mon, 15 Jul 2013 11:15:32 +0300 (EEST)	[thread overview]
Message-ID: <20130715081532.52D85E0090@blue.fi.intel.com> (raw)
In-Reply-To: <1373675551-18684-1-git-send-email-andi@firstfloor.org>

Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
> 
> glibc calloc() has an optimization to not explicitely memset()
> very large calloc allocations that just came from mmap(),
> because they are known to be zero.
> 
> This could result in the perf memcpy benchmark reading only from
> the zero page, which gives unrealistic results.
> 
> Always call memset explicitly on the source area to avoid this problem.
> 
> Cc: h.mitake@gmail.com
> Cc: kirill.shutemov@linux.intel.com
> Signed-off-by: Andi Kleen <ak@linux.intel.com>

Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>

> ---
>  tools/perf/bench/mem-memcpy.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/tools/perf/bench/mem-memcpy.c b/tools/perf/bench/mem-memcpy.c
> index 93c83e3..690f75f 100644
> --- a/tools/perf/bench/mem-memcpy.c
> +++ b/tools/perf/bench/mem-memcpy.c
> @@ -117,6 +117,8 @@ static void alloc_mem(void **dst, void **src, size_t length)
>  	*src = zalloc(length);
>  	if (!src)
>  		die("memory allocation failed - maybe length is too large?\n");
> +	/* Make sure to always replace the zero pages even if MMAP_THRESH is crossed */
> +	memset(src, 0, length);
>  }
>  
>  static u64 do_memcpy_cycle(memcpy_t fn, size_t len, bool prefault)
> -- 
> 1.8.1.4

-- 
 Kirill A. Shutemov

       reply	other threads:[~2013-07-15  8:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1373675551-18684-1-git-send-email-andi@firstfloor.org>
2013-07-15  8:15 ` Kirill A. Shutemov [this message]
2013-07-15 12:16   ` Hitoshi Mitake
2013-07-16 10:11 ` Kirill A. Shutemov
2013-07-16 13:14   ` Hitoshi Mitake
2013-07-16 14:20   ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130715081532.52D85E0090@blue.fi.intel.com \
    --to=kirill.shutemov@linux.intel.com \
    --cc=acme@infradead.org \
    --cc=ak@linux.jf.intel.com \
    --cc=andi@firstfloor.org \
    --cc=h.mitake@gmail.com \
    --cc=kirill.shutemov@linux.jf.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome