From: Anup Sharma <anupnewsmail@gmail.com>
To: Ian Rogers <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org, acme@kernel.org,
namhyung@kernel.org, irogers+gsoc22@google.com,
anupnewsmail@gmail.com
Subject: Re: [RFC] Open Source Contribution | GSoC Perf
Date: Fri, 17 Mar 2023 16:27:36 +0530 [thread overview]
Message-ID: <ZBRHoIuv2g6RTdAx@yoga> (raw)
In-Reply-To: <CAP-5=fVT3vh8j8FVAdr2Zp2bTpCxdLGW4Gkndb6-mmNdRcW7ug@mail.gmail.com>
On Tue, Mar 07, 2023 at 10:57:23AM -0800, Ian Rogers wrote:
> On Mon, Mar 6, 2023 at 1:04 PM Anup Sharma <anupnewsmail@gmail.com> wrote:
> >
> > Hello, Perf!
> > I'm interested in joining the perf community and learning more about how to start contributing because of my desire to learn more about the Linux kernel and performance.
> > I've only recently started using Perf Tool, but I'm really enjoying seeing the metrics and outcomes. I want to resolve a few inconsistencies I found on a wiki page while learning, so if you have any suggestions, please let me know.
> > 1. LINK BROKEN under Tutorial-> Linux Sourcecode: /tools/perf (hyperlink: ) correct (
> > 2. LINK BROKEN under Hardware Reference -> Performance Counters for Linux: hyperlink for PCL core kernel data structures, PCL core kernel internals, perf tool internals are not available. Can anyone help me to know why this contents are not available on wiki?
> > 3. ALLIGNMENT : Under Glossary -> BPF counter, Off-CPU, Multiplexing is not alliged properly.
> > 4. INFO MISSING: Under Glossary -> offcore is TODO.
> >
> > I've also invested some time going though Brendan Gregg conference talk and wiki page, I'd be delighted to contribute to any of the open tasks!
> > Thank you all for your time.
>
> Thanks Anup!
>
> Updating the wiki is great! I was looking at your changes, I'd
> encourage linux-perf-users to checkout updates at:
> https://perf.wiki.kernel.org/index.php/Special:RecentChanges
>
> I wanted to give some feedback on just one of the changes:
> https://perf.wiki.kernel.org/index.php?title=Tutorial&curid=22&diff=3921&oldid=3520
> The maintainer's source tree is at:
> https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/
> which gets integrated into the main Linus tree at:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
> I think it would be better to use these rather than which given the
> version number in the URL looks quite out-of-date compared to Linux
> 6.2:
> http://lxr.linux.no/linux+v2.6.39/tools/perf/
>
Done.
> Thanks,
> Ian
>
> > With regards,
> > Anup Sharma
next prev parent reply other threads:[~2023-03-17 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 21:04 [RFC] Open Source Contribution | GSoC Perf Anup Sharma
2023-03-07 18:57 ` Ian Rogers
2023-03-17 10:57 ` Anup Sharma [this message]
2023-03-17 11:08 ` Anup Sharma
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=ZBRHoIuv2g6RTdAx@yoga \
--to=anupnewsmail@gmail.com \
--cc=acme@kernel.org \
--cc=irogers+gsoc22@google.com \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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).