From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
adrian.hunter@intel.com
Subject: Re: [PATCH 0/2] perf: Allow closing siblings' file descriptors
Date: Thu, 9 Jul 2020 11:30:34 +0300 [thread overview]
Message-ID: <9a6e9cd6-1ba2-3519-563f-c1eb45329539@linux.intel.com> (raw)
In-Reply-To: <20200708151635.81239-1-alexander.shishkin@linux.intel.com>
Hi Alex,
On 08.07.2020 18:16, Alexander Shishkin wrote:
> Hi guys,
>
> I've been looking at reducing the number of open file descriptors per perf
> session. If we retain one descriptor per event, in a large group they add
> up. At the same time, we're not actually using them for anything after the
> SET_OUTPUT and maybe SET_FILTER ioctls. So, this series is a stab at that.
PERF_EVENT_IOC_ENABLE, PERF_EVENT_IOC_DISABLE ioctls are still assumed to
work, right?
Asking w.r.t. functionality on --control fd:ctl_fd[,ack_fd] option for stat
and record modes [1].
Thanks,
Alexey
[1] https://lore.kernel.org/lkml/4af50c95-36f6-7a61-5a22-2949970fe7a5@linux.intel.com/
>
> So, I added a new flag to the perf_event_open() that tells perf to keep
> the event around after its file descriptor gets closed, for as long as its
> group leader is alive. Since this is a new behavior, the flag is an opt-in.
>
> I also hacked this into the perf tool (mostly perf record, but I'll hack
> stat as well if this general approach is agreeable).
>
> Alexander Shishkin (2):
> perf: Add closing sibling events' file descriptors
> perf record: Support closing siblings' file descriptors
>
> include/linux/perf_event.h | 7 ++
> include/uapi/linux/perf_event.h | 1 +
> kernel/events/core.c | 149 +++++++++++++++++-------
> tools/include/uapi/linux/perf_event.h | 1 +
> tools/lib/perf/evlist.c | 30 ++++-
> tools/lib/perf/evsel.c | 21 ++++
> tools/lib/perf/include/internal/evsel.h | 4 +
> tools/perf/builtin-record.c | 48 ++++++--
> tools/perf/util/cpumap.c | 4 +
> tools/perf/util/evlist.c | 4 +-
> tools/perf/util/evsel.c | 17 ++-
> tools/perf/util/evsel.h | 3 +
> 12 files changed, 234 insertions(+), 55 deletions(-)
>
next prev parent reply other threads:[~2020-07-09 8:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 15:16 Alexander Shishkin
2020-07-08 15:16 ` [PATCH 1/2] perf: Add closing sibling events' " Alexander Shishkin
2020-08-06 8:35 ` peterz
2020-08-06 15:32 ` Andi Kleen
2020-08-10 13:57 ` Alexander Shishkin
2020-08-10 14:45 ` Andi Kleen
2020-08-10 20:36 ` Peter Zijlstra
2020-08-11 8:12 ` Alexey Budankov
2020-08-11 14:29 ` Andi Kleen
2020-08-11 14:47 ` David Laight
2020-08-11 18:03 ` Andi Kleen
2020-08-11 21:06 ` David Laight
2020-08-11 9:47 ` Alexander Shishkin
2020-08-11 14:34 ` Andi Kleen
2020-08-11 16:21 ` Alexander Shishkin
2020-08-11 18:02 ` Andi Kleen
2020-07-08 15:16 ` [PATCH 2/2] perf record: Support closing siblings' " Alexander Shishkin
2020-07-08 21:09 ` Jiri Olsa
2020-07-16 8:42 ` [perf record] d65f0cbbc6: perf-sanity-tests.Setup_struct_perf_event_attr.fail kernel test robot
2020-07-09 8:30 ` Alexey Budankov [this message]
2020-08-06 6:15 ` [PATCH 0/2] perf: Allow closing siblings' file descriptors Adrian Hunter
2020-08-06 8:37 ` peterz
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=9a6e9cd6-1ba2-3519-563f-c1eb45329539@linux.intel.com \
--to=alexey.budankov@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
Powered by JetHome