linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: M V V S Manoj Kumar <mvvsmanojkumar.mailinglist@gmail.com>
To: linux-perf-users@vger.kernel.org
Subject: Proposal for Roofline Support in perf
Date: Thu, 7 Mar 2024 10:50:25 +0530	[thread overview]
Message-ID: <CAMZOccS0NcTSSHkJEiM6X5pM95OT98iwz152303qPnKdw49azA@mail.gmail.com> (raw)

My name is M V V S Manoj Kumar, an open-source contributor to GCC with
contributions to GCCRS [see
here](https://github.com/Rust-GCC/gccrs/issues?q=assignee%3Amvvsmk+is%3Aclosed)
and a research intern with the compilers group at IITH [website
link](https://compilers.cse.iith.ac.in/), India. I'm writing to
propose a project that aims to add roofline support to the perf tool.

During my internship, I've gained significant experience in roofline
analysis. This project involves incorporating micro-benchmarks to
generate roofline data, initially using the Original roofline model
outlined in the following paper:
[paper](https://people.eecs.berkeley.edu/~kubitron/cs252/handouts/papers/RooflineVyNoYellow.pdf).
We can later explore incorporating cache-aware rooflines
[paper](https://www.inesc-id.pt/ficheiros/publicacoes/9068.pdf).

For testing and comparison, I have access to a laptop with an Intel
10300H processor. This allows for comparison with tools like Intel
Advisor, Likwid, and other open source toolkits.

I believe your mentorship would be invaluable in guiding me through
this project. I'd like to explore the perf codebase to gain a better
understanding of its structure. I would be grateful for any advice you
may have regarding exploring the codebase, suggesting initial "easy
hacks" or beginner-friendly issues to contribute to, and pointing me
towards appropriate communication channels within the perf community.

Thank you for your time and consideration.

Sincerely,

M V V S Manoj Kumar
mailing-list email : mvvsmanojkumar.mailinglist@gmail.com
personal email : mvvsmanojkumar@gmail.com
official email : compiler.intern.24005@cse.iith.ac.in

                 reply	other threads:[~2024-03-07  5:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAMZOccS0NcTSSHkJEiM6X5pM95OT98iwz152303qPnKdw49azA@mail.gmail.com \
    --to=mvvsmanojkumar.mailinglist@gmail.com \
    --cc=linux-perf-users@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;
as well as URLs for NNTP newsgroup(s).