From: Yang Shi <shy828301@gmail.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: lsf-pc@lists.linux-foundation.org,
olivier.singla@amperecomputing.com,
"Christoph Lameter (Ampere)" <cl@gentwo.org>,
Linux MM <linux-mm@kvack.org>, Michal Hocko <mhocko@suse.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [LSF/MM/BPF TOPIC] Multi-sized THP performance benchmarks and analysis on ARM64
Date: Tue, 2 Apr 2024 13:04:17 -0700 [thread overview]
Message-ID: <CAHbLzkpUac5H4xGQhwAAowzFb6QDiWm9h4UgzxUcoFNauV+n7A@mail.gmail.com> (raw)
In-Reply-To: <20240401191614.00007c83@Huawei.com>
On Mon, Apr 1, 2024 at 11:16 AM Jonathan Cameron
<Jonathan.Cameron@huawei.com> wrote:
>
> On Thu, 28 Mar 2024 09:47:04 -0700
> Yang Shi <shy828301@gmail.com> wrote:
>
> > We just made some progress regarding multi-sized THP benchmarking on
> > the ARM64 platform. So I'd like to propose the topic "Multi-sized THP
> > performance benchmark on ARM64" for MM track.
> >
> > We ran a series of benchmarks on Ampere Altra platform using some
> > popular workloads in the cloud: In-memory databases, kernel
> > compilation, etc, using different sized huge pages: 2M, 128K, 64K and
> > others.
> >
> > This topic will cover:
> > - The benchmark data of some popular workloads in Cloud
> > - The performance analysis (where the gain came from, the
> > contributing factors, etc)
> > - Th recommended page sizes which can achieve overall decent performance gain
> >
>
> Sounds like useful data, but is it a suitable topic for LSF-MM?
> What open questions etc is it raising?
>
> I'm very interested in seeing your results, but maybe this isn't the best path
> for them.
Thanks for showing interest. Hopefully the benchmark data also can
help us for the direction of further optimizations, and I hope this is
also a part of the session.
>
> Jonathan
next prev parent reply other threads:[~2024-04-02 20:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 16:47 Yang Shi
2024-04-01 18:16 ` Jonathan Cameron
2024-04-02 20:04 ` Yang Shi [this message]
2024-04-04 18:57 ` Christoph Lameter (Ampere)
2024-04-04 19:33 ` David Hildenbrand
2024-04-09 18:41 ` Yang Shi
2024-04-09 18:44 ` David Hildenbrand
2024-04-30 14:41 ` Michal Hocko
2024-05-01 16:37 ` Yang Shi
2024-04-08 16:30 ` Matthew Wilcox
2024-04-08 18:56 ` Zi Yan
2024-04-09 10:47 ` Ryan Roberts
2024-06-25 11:12 ` Ryan Roberts
2024-06-25 18:11 ` Christoph Lameter (Ampere)
2024-06-26 10:47 ` Ryan Roberts
2024-06-27 20:54 ` Yang Shi
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=CAHbLzkpUac5H4xGQhwAAowzFb6QDiWm9h4UgzxUcoFNauV+n7A@mail.gmail.com \
--to=shy828301@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=cl@gentwo.org \
--cc=dan.j.williams@intel.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@suse.com \
--cc=olivier.singla@amperecomputing.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