From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andi Kleen <ak@linux.intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Stephane Eranian <eranian@google.com>,
Ian Rogers <irogers@google.com>, Song Liu <songliubraving@fb.com>,
"Jin, Yao" <yao.jin@linux.intel.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kees Cook <keescook@chromium.org>,
Jonatan Corbet <corbet@lwn.net>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: BoF on LPC 2019 : Linux Perf advancements for compute intensive and server systems
Date: Mon, 26 Aug 2019 14:36:48 +0300 [thread overview]
Message-ID: <43216530-4410-6cc4-aa4a-51fa7e7c1b0c@linux.intel.com> (raw)
Hi,
There is a BoF session scheduled on Linux Plumbers Conference 2019 event.
If you plan attend the event feel free to join and discuss about the BoF
topic and beyond:
Linux Perf advancements for compute intensive and server systems:
"Modern server and compute intensive systems are naturally built around
several top performance CPUs with large amount of cores and equipped
by shared memory that spans a number of NUMA domains. Compute intensive
workloads usually implement highly parallel CPU bound cyclic codes
performing mathematics calculations that reference data located in
the shared memory. Performance observability and profiling of these
workloads on such systems have unique characteristics and impose specific
requirements on software performance tools. The requirements include
tools CPU scalability, coping with high rate and volume of collected
performance data as well as NUMA awareness. In order to fulfill that
requirements a number of extensions have been implemented in Linux Perf
tool that are currently a part of the Linux kernel source tree
[1], [2], [3], [4]"
Best regards,
Alexey
[1] https://marc.info/?l=linux-kernel&m=154149439404555&w=2
[2] https://marc.info/?l=linux-kernel&m=154817912621465&w=2
[3] https://marc.info/?l=linux-kernel&m=155293062518459&w=2
[4] https://www.kernel.org/doc/html/latest/admin-guide/perf-security.html
next reply other threads:[~2019-08-26 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 11:36 Alexey Budankov [this message]
2019-08-26 13:55 ` BoF on LPC 2019 : Linux Perf advancements for compute intensive and server systems Arnaldo Carvalho de Melo
2019-08-26 14:25 ` Alexey Budankov
2019-08-26 17:57 ` Andi Kleen
2019-08-26 22:10 ` Arnaldo Carvalho de Melo
2019-08-27 7:48 ` Jiri Olsa
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=43216530-4410-6cc4-aa4a-51fa7e7c1b0c@linux.intel.com \
--to=alexey.budankov@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=corbet@lwn.net \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=yao.jin@linux.intel.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;
as well as URLs for NNTP newsgroup(s).