From: David Laight <David.Laight@ACULAB.COM>
To: 'Paul Clarke' <pc@us.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"acme@kernel.org" <acme@kernel.org>,
"jolsa@redhat.com" <jolsa@redhat.com>
Cc: "brueckner@linux.vnet.ibm.com" <brueckner@linux.vnet.ibm.com>,
"schwidefsky@de.ibm.com" <schwidefsky@de.ibm.com>,
"heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>
Subject: RE: [PATCH 1/3] perf alias: Remove trailing newline when reading sysfs files
Date: Fri, 15 Jun 2018 09:10:52 +0000 [thread overview]
Message-ID: <30f3ac625d734674aa6697440aa3253f@AcuMS.aculab.com> (raw)
In-Reply-To: <c29a4b36-a2db-b1d9-a5c7-a0c0806970ab@us.ibm.com>
From: Paul Clarke
> Sent: 14 June 2018 14:18
...
> > + /* Remove trailing newline from sysfs file */
> > + cp = strrchr(buf, '\n');
> > + if (cp)
> > + *cp = '\0';
>
> A nit, perhaps, but this will search backwards through the entire string if a newline is not found,
> which is the most common case, I presume. Would it be more efficient to just look at the last
> character? Something like:
> i = strlen(buf);
> if (i > 0 && buf[i-1] == '\n')
> buf[i-1] = '\0';
Worse it will do horrid things of the output has multiple lines of text
without a newline at the end.
Both strlen() and strrhr() need to scan the entire string.
However since strlen is only looking for one value it should be much
more efficient - especially on 64bit systems where shifts and bit
operations can be used to find the 64bit word containing the first
zero byte.
I suspect rtrim() has an extra data cache miss.
David
next prev parent reply other threads:[~2018-06-15 9:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 11:48 Thomas Richter
2018-06-14 11:48 ` [PATCH 2/3] perf alias: Rebuild alias expression string to make it comparable Thomas Richter
2018-06-14 13:53 ` Paul Clarke
2018-06-14 14:16 ` Thomas-Mich Richter
2018-06-15 8:12 ` Jiri Olsa
2018-06-15 9:09 ` Thomas-Mich Richter
2018-06-15 9:27 ` Jiri Olsa
2018-06-14 11:48 ` [PATCH 3/3] perf stat: Remove duplicate event counting Thomas Richter
2018-06-15 8:21 ` Jiri Olsa
2018-06-15 8:56 ` Thomas-Mich Richter
2018-06-19 15:17 ` Arnaldo Carvalho de Melo
2018-06-19 18:24 ` Jiri Olsa
2018-06-14 13:17 ` [PATCH 1/3] perf alias: Remove trailing newline when reading sysfs files Paul Clarke
2018-06-14 14:10 ` Thomas-Mich Richter
2018-06-15 9:10 ` David Laight [this message]
2018-06-14 14:05 ` Arnaldo Carvalho de Melo
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=30f3ac625d734674aa6697440aa3253f@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=acme@kernel.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=pc@us.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=tmricht@linux.ibm.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