From: "Wangnan (F)" <wangnan0@huawei.com>
To: <kan.liang@intel.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf tool: Don't discard prev in backward mode
Date: Thu, 12 Oct 2017 23:12:37 +0800 [thread overview]
Message-ID: <9ff681c0-fb71-9e65-3692-7f92f27cfbf5@huawei.com> (raw)
In-Reply-To: <20171013231628.27509-1-wangnan0@huawei.com>
Hi Kan, Please see if this patch works for you.
On 2017/10/14 7:16, Wang Nan wrote:
> Perf record can switch output. The new output should only store the
> data after switching. However, in overwrite backward mode, the new
> output still have the data from old output. That also brings extra overhead.
>
> At the end of mmap_read, the position of processed ring buffer is
> saved in md->prev. Next mmap_read should be end in md->prev if it is
> not overwriten. That avoids to process duplicate data.
> However, the md->prev is discarded. So next mmap_read has to process
> whole valid ring buffer, which probably include the old processed
> data.
>
> Avoid calling backward_rb_find_range() when md->prev is still
> available.
>
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> Cc: Liang Kan <kan.liang@intel.com>
> ---
> tools/perf/util/mmap.c | 33 +++++++++++++++------------------
> 1 file changed, 15 insertions(+), 18 deletions(-)
>
> diff --git a/tools/perf/util/mmap.c b/tools/perf/util/mmap.c
> index 9fe5f9c..df1de55 100644
> --- a/tools/perf/util/mmap.c
> +++ b/tools/perf/util/mmap.c
> @@ -287,18 +287,6 @@ static int backward_rb_find_range(void *buf, int mask, u64 head, u64 *start, u64
> return -1;
> }
>
> -static int rb_find_range(void *data, int mask, u64 head, u64 old,
> - u64 *start, u64 *end, bool backward)
> -{
> - if (!backward) {
> - *start = old;
> - *end = head;
> - return 0;
> - }
> -
> - return backward_rb_find_range(data, mask, head, start, end);
> -}
> -
> int perf_mmap__push(struct perf_mmap *md, bool overwrite, bool backward,
> void *to, int push(void *to, void *buf, size_t size))
> {
> @@ -310,19 +298,28 @@ int perf_mmap__push(struct perf_mmap *md, bool overwrite, bool backward,
> void *buf;
> int rc = 0;
>
> - if (rb_find_range(data, md->mask, head, old, &start, &end, backward))
> - return -1;
> + start = backward ? head : old;
> + end = backward ? old : head;
>
> if (start == end)
> return 0;
>
> size = end - start;
> if (size > (unsigned long)(md->mask) + 1) {
> - WARN_ONCE(1, "failed to keep up with mmap data. (warn only once)\n");
> + if (!backward) {
> + WARN_ONCE(1, "failed to keep up with mmap data. (warn only once)\n");
>
> - md->prev = head;
> - perf_mmap__consume(md, overwrite || backward);
> - return 0;
> + md->prev = head;
> + perf_mmap__consume(md, overwrite || backward);
> + return 0;
> + }
> +
> + /*
> + * Backward ring buffer is full. We still have a chance to read
> + * most of data from it.
> + */
> + if (backward_rb_find_range(data, md->mask, head, &start, &end))
> + return -1;
> }
>
> if ((start & md->mask) + size != (end & md->mask)) {
next prev parent reply other threads:[~2017-10-12 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 23:16 Wang Nan
2017-10-12 15:12 ` Wangnan (F) [this message]
2017-10-12 15:36 ` Liang, Kan
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=9ff681c0-fb71-9e65-3692-7f92f27cfbf5@huawei.com \
--to=wangnan0@huawei.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®