From: Ingo Molnar <mingo@elte.hu>
To: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] perf bench: Add "all" pseudo subsystem and "all" pseudo suite
Date: Sat, 12 Dec 2009 11:55:54 +0100 [thread overview]
Message-ID: <20091212105554.GA9345@elte.hu> (raw)
In-Reply-To: <1260614277-6059-1-git-send-email-mitake@dcl.info.waseda.ac.jp>
* Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp> wrote:
> | # Running mem/memcpy benchmark... # Second mem !?
> | # Copying 1MB Bytes from 0x7ff33e920010 to 0x7ff3401ae010 ...
> |
> | 841.042893 MB/Sec
>
> mem subsystem was executed twice!
i saw something similar some time ago but thought it got fixed. Maybe
some fork() related trouble?
Ingo
next prev parent reply other threads:[~2009-12-12 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091124152051.GA21821@elte.hu>
2009-12-12 10:37 ` Hitoshi Mitake
2009-12-12 10:55 ` Ingo Molnar [this message]
2009-12-13 8:01 ` [PATCH v2] " Hitoshi Mitake
2009-12-14 7:51 ` Ingo Molnar
2009-12-14 14:46 ` Hitoshi Mitake
2009-12-14 7:57 ` [tip:perf/urgent] " tip-bot for Hitoshi Mitake
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=20091212105554.GA9345@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=paulus@samba.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