From: Chuck Ebbert <76306.1226@compuserve.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: Hugh Dickins <hugh@veritas.com>,
Akinobu Mita <mita@miraclelinux.com>,
Keith Owens <kaos@ocs.com.au>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Jesper Juhl <jesper.juhl@gmail.com>,
Arjan van de Ven <arjan@infradead.org>, Andi Kleen <ak@suse.de>
Subject: Re: [PATCH 3/4] compact print_symbol() output
Date: Wed, 18 Jan 2006 01:08:09 -0500 [thread overview]
Message-ID: <200601180110_MC3-1-B60F-59DE@compuserve.com> (raw)
In-Reply-To: <200601180325.k0I3P8tF008591@turing-police.cc.vt.edu>
On Tue, 17 Jan 2006 at 22:25:07 -0500, Valdis.Kletnieks wrote:
> On Tue, 17 Jan 2006 22:05:27 EST, Chuck Ebbert said:
>
> > OK, how about this: remove the "0x" from the function size, i.e. print:
> >
> > kernel_symbol+0xd3/10e
> >
> > instead of:
> >
> > kernel_symbol+0xd3/0x10e
> >
> > This saves two characters per symbol and it should still be clear that
> > the second number is hexadecimal.
>
> Good. Now repeat for a function that's 6 bytes shorter.
OK, I probably should have done that:
kernel_symbol+0xd3/108
My point is that if the "numerator" is hex you should assume the
"denominator" is too.
--
Chuck
Currently reading: _Einstein's Bridge_ by John Cramer
next reply other threads:[~2006-01-18 6:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 6:08 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 3:05 Chuck Ebbert
2006-01-18 3:15 ` Keith Owens
2006-01-18 3:25 ` Valdis.Kletnieks
2006-01-17 10:13 [PATCH 0/4] compact call trace Akinobu Mita
2006-01-17 10:15 ` [PATCH 3/4] compact print_symbol() output Akinobu Mita
2006-01-17 10:34 ` Keith Owens
2006-01-17 10:52 ` Jesper Juhl
2006-01-17 10:58 ` Akinobu Mita
2006-01-17 11:01 ` Keith Owens
2006-01-17 11:23 ` Akinobu Mita
2006-01-17 15:01 ` Hugh Dickins
2006-01-17 15:01 ` Andi Kleen
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=200601180110_MC3-1-B60F-59DE@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--cc=hugh@veritas.com \
--cc=jesper.juhl@gmail.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mita@miraclelinux.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
all inboxes | Powered by JetHome®