From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Franck Bui-Huu <vagabon.xyz@gmail.com>,
linux-kernel@vger.kernel.org, 2nddept-manager@sdl.hitachi.co.jp
Subject: Re: [PATCH] perf-probe: no need to initialize the entire temporary buffers in synthesize_perf_probe_point()
Date: Fri, 24 Dec 2010 11:14:41 -0200 [thread overview]
Message-ID: <20101224131441.GA3128@ghostprotocols.net> (raw)
In-Reply-To: <4D142591.2030101@hitachi.com>
Em Fri, Dec 24, 2010 at 01:46:09PM +0900, Masami Hiramatsu escreveu:
> (2010/12/24 0:27), Franck Bui-Huu wrote:
> > This patches only put a single null byte at the beginning of each
> > temporary buffers line[], offs[], file[] instead of filling their
> > full contents with null bytes.
> Hmm, sorry but NAK it.
> IMHO, with modern chips, the original code has no problem from the
> viewpoint of memory access (all are cached and no need to access just
> one byte) nor a bottleneck.
> I'd rather use '= ""' style initialization for local variables from the
> viewpoint of readability.
No strong feelings here, not really a fast path, just learned something
new, I thought that that kind of initialization would be equivalent to
what Franck proposed, but gcc really uses the most efficient way of
zeroing the whole string (movq for things like that, and rep stos for
bigger arrays, etc).
> Anyway, thank you for looking into the code :-)
Yes, please continue sending your improvements and fixes!
Masami, what about the fixes Franck sent, clould you please send ACK or
NACKs for those?
- Arnaldo
next prev parent reply other threads:[~2010-12-24 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 15:27 [PATCH] perf-probe: no need to initialize the entire temporary buffers in synthesize_perf_probe_point() Franck Bui-Huu
2010-12-24 4:46 ` Masami Hiramatsu
2010-12-24 13:14 ` Arnaldo Carvalho de Melo [this message]
2010-12-27 21:06 ` Franck Bui-Huu
2010-12-27 21:01 ` Franck Bui-Huu
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=20101224131441.GA3128@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=2nddept-manager@sdl.hitachi.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=vagabon.xyz@gmail.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