From: Leo Yan <leo.yan@linaro.org>
To: Carsten Haitzler <carsten.haitzler@foss.arm.com>
Cc: linux-kernel@vger.kernel.org, coresight@lists.linaro.org,
suzuki.poulose@arm.com, mathieu.poirier@linaro.org,
mike.leach@linaro.org, linux-perf-users@vger.kernel.org,
acme@kernel.org
Subject: Re: [PATCH 3/3] perf test: Add coresight tests to guage quality of data generated
Date: Fri, 27 May 2022 00:08:17 +0800 [thread overview]
Message-ID: <20220526160817.GE795802@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20220526082039.GA795802@leoy-ThinkPad-X240s>
On Thu, May 26, 2022 at 04:20:39PM +0800, Leo Yan wrote:
[...]
> Yes, my Juno board has 8GB but I also have DB410c with 1GB with quad
> coes [1]. I am still concern for 256MB buffer size, it's not friendly for
> embedded system, and even not good for server. For example, if we run
> this testing on Arm server with 96 cores (like Hisilicon D06 board),
> then we need the buffer size is:
>
> 256MiB * 96 = 16GiB
Correct for my bad math... here should be 256MiB * 96 = 24GiB.
next prev parent reply other threads:[~2022-05-26 16:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 12:28 [PATCH 1/3] perf test: Shell - Limit to only run executable scripts in tests carsten.haitzler
2022-03-09 12:28 ` [PATCH 2/3] perf test: Shell - only run .sh shell files to skip other files carsten.haitzler
2022-04-10 2:28 ` Leo Yan
2022-04-21 16:21 ` Carsten Haitzler
2022-05-26 10:14 ` Leo Yan
2022-06-13 13:08 ` Carsten Haitzler
2022-06-15 9:14 ` Leo Yan
2022-03-09 12:28 ` [PATCH 3/3] perf test: Add coresight tests to guage quality of data generated carsten.haitzler
2022-04-10 8:30 ` Leo Yan
2022-04-21 17:38 ` Carsten Haitzler
2022-05-26 8:20 ` Leo Yan
2022-05-26 16:08 ` Leo Yan [this message]
2022-06-13 14:15 ` Carsten Haitzler
2022-05-30 16:27 ` Mathieu Poirier
2022-05-30 16:47 ` Mathieu Poirier
2022-06-13 12:53 ` Carsten Haitzler
2022-06-13 13:00 ` Carsten Haitzler
2022-04-10 1:24 ` [PATCH 1/3] perf test: Shell - Limit to only run executable scripts in tests Leo Yan
2022-04-11 19:08 ` Arnaldo Carvalho de Melo
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=20220526160817.GE795802@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=acme@kernel.org \
--cc=carsten.haitzler@foss.arm.com \
--cc=coresight@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
/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