From: Jiri Olsa <jolsa@redhat.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Petr Mladek <pmladek@suse.com>,
Andrey Zhizhikin <andrey.z@gmail.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kan Liang <kan.liang@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 4/5] tools api: add a lightweight buffered reading api
Date: Thu, 2 Apr 2020 15:41:37 +0200 [thread overview]
Message-ID: <20200402134137.GL2518490@krava> (raw)
In-Reply-To: <20200401233945.133550-5-irogers@google.com>
On Wed, Apr 01, 2020 at 04:39:44PM -0700, Ian Rogers wrote:
> The synthesize benchmark shows the majority of execution time going to
> fgets and sscanf, necessary to parse /proc/pid/maps. Add a new buffered
> reading library that will be used to replace these calls in a follow-up
> CL.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/lib/api/io.h | 103 +++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 103 insertions(+)
> create mode 100644 tools/lib/api/io.h
>
> diff --git a/tools/lib/api/io.h b/tools/lib/api/io.h
> new file mode 100644
> index 000000000000..e88d76c59440
> --- /dev/null
> +++ b/tools/lib/api/io.h
> @@ -0,0 +1,103 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +/*
> + * Lightweight buffered reading library.
> + *
> + * Copyright 2019 Google LLC.
> + */
missing the recursion header check
#ifndef __PERF_IO_H
#define __PERF_IO_H
> +
> +struct io {
> + /* File descriptor being read/ */
> + int fd;
> + /* Size of the read buffer. */
> + unsigned int buf_len;
> + /* Pointer to storage for buffering read. */
> + char *buf;
> + /* End of the storage. */
> + char *end;
> + /* Currently accessed data pointer. */
> + char *data;
> + /* Set true on when the end of file on read error. */
> + bool eof;
> +};
> +
> +static inline void init_io(struct io *io, int fd,
> + char *buf, unsigned int buf_len)
> +{
> + io->fd = fd;
> + io->buf_len = buf_len;
> + io->buf = buf;
> + io->end = buf;
> + io->data = buf;
> + io->eof = false;
> +}
looks good, could you please add io__ prefix for all functions?
thanks,
jirka
> +
> +/* Reads one character from the "io" file with similar semantics to fgetc. */
> +static inline int get_char(struct io *io)
> +{
> + char *ptr = io->data;
> +
> + if (ptr == io->end) {
> + ssize_t n = read(io->fd, io->buf, io->buf_len);
> +
> + if (n <= 0) {
> + io->eof = true;
> + return -1;
> + }
> + ptr = &io->buf[0];
> + io->end = &io->buf[n];
> + }
> + io->data = ptr + 1;
> + return *ptr;
> +}
> +
> +/* Read a hexadecimal value with no 0x prefix into the out argument hex.
> + * Returns -1 on error or if nothing is read, otherwise returns the character
> + * after the hexadecimal value.
> + */
> +static inline int get_hex(struct io *io, __u64 *hex)
> +{
> + bool first_read = true;
> +
> + *hex = 0;
> + while (true) {
> + char ch = get_char(io);
> +
> + if (ch < 0)
> + return ch;
> + if (ch >= '0' && ch <= '9')
> + *hex = (*hex << 4) | (ch - '0');
> + else if (ch >= 'a' && ch <= 'f')
> + *hex = (*hex << 4) | (ch - 'a' + 10);
> + else if (ch >= 'A' && ch <= 'F')
> + *hex = (*hex << 4) | (ch - 'A' + 10);
> + else if (first_read)
> + return -1;
> + else
> + return ch;
> + first_read = false;
> + }
> +}
> +
> +/* Read a decimal value into the out argument dec.
> + * Returns -1 on error or if nothing is read, otherwise returns the character
> + * after the decimal value.
> + */
> +static inline int get_dec(struct io *io, __u64 *dec)
> +{
> + bool first_read = true;
> +
> + *dec = 0;
> + while (true) {
> + char ch = get_char(io);
> +
> + if (ch < 0)
> + return ch;
> + if (ch >= '0' && ch <= '9')
> + *dec = (*dec * 10) + ch - '0';
> + else if (first_read)
> + return -1;
> + else
> + return ch;
> + first_read = false;
> + }
> +}
> --
> 2.26.0.rc2.310.g2932bb562d-goog
>
next prev parent reply other threads:[~2020-04-02 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 23:39 [PATCH 0/5] Benchmark and improve event synthesis performance Ian Rogers
2020-04-01 23:39 ` [PATCH 1/5] perf bench: add event synthesis benchmark Ian Rogers
2020-04-02 13:41 ` Jiri Olsa
2020-04-01 23:39 ` [PATCH 2/5] tools api fs: make xxx__mountpoint() more scalable Ian Rogers
2020-04-01 23:39 ` [PATCH 3/5] perf synthetic-events: save 4kb from 2 stack frames Ian Rogers
2020-04-01 23:39 ` [PATCH 4/5] tools api: add a lightweight buffered reading api Ian Rogers
2020-04-02 13:41 ` Jiri Olsa [this message]
2020-04-01 23:39 ` [PATCH 5/5] perf synthetic events: Remove use of sscanf from /proc reading Ian Rogers
2020-04-02 13:40 ` Jiri Olsa
2020-04-02 13:41 ` 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=20200402134137.GL2518490@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrey.z@gmail.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--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=pmladek@suse.com \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.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).