From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [RFC][PATCH 3/3] perf_counter: new output ABI - part 1
Date: Fri, 20 Mar 2009 20:09:12 +0100 [thread overview]
Message-ID: <20090320190912.GF6224@elte.hu> (raw)
In-Reply-To: <20090320151735.008338484@chello.nl>
* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> Rework the output ABI
>
> use sys_read() only for instant data and provide mmap() output for
> all async overflow data.
i like this.
> The first mmap() determines the size of the output buffer. The
> mmap() size must be a PAGE_SIZE multiple of 1+pages, where pages
> must be a power of 2 or 0. Further mmap()s of the same fd must
> have the same size. Once all maps are gone, you can again mmap()
> with a new size.
>
> In case of 0 extra pages there is no data output and the first
> page only contains meta data.
>
> When there are data pages, a poll() event will be generated for
> each full page of data. Furthermore, the output is circular. This
> means that although 1 page is a valid configuration, its useless,
> since we'll start overwriting it the instant we report a full
> page.
i think it would still be nice to allow plain old-fashioned
poll()+read() loops ... but the logistics of that seem difficult.
mmap() seems to fit this better - and it's probably faster as well.
(as we have to construct the kernel-space pages anyway, so mapping
them isnt that big of an issue)
per-CPU-ness will be handled naturally via per-cpu counters.
Paul, can you see any hole/quirkiness in this scheme?
Ingo
next prev parent reply other threads:[~2009-03-20 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 15:15 [RFC][PATCH 0/3] perf_counter: mmap output of overflow data Peter Zijlstra
2009-03-20 15:15 ` [RFC][PATCH 1/3] perf_counter: add an mmap method to allow userspace to read hardware counters Peter Zijlstra
2009-03-20 15:15 ` [RFC][PATCH 2/3] mutex: add atomic_dec_and_mutex_lock] Peter Zijlstra
2009-03-20 15:15 ` [RFC][PATCH 3/3] perf_counter: new output ABI - part 1 Peter Zijlstra
2009-03-20 19:09 ` Ingo Molnar [this message]
2009-03-21 9:45 ` Paul Mackerras
2009-03-21 10:29 ` Peter Zijlstra
2009-03-21 16:21 ` Ingo Molnar
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=20090320190912.GF6224@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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