From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Alexey Dobriyan" <adobriyan@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Some love to default profiler
Date: Thu, 5 Jul 2007 01:50:27 +0200 [thread overview]
Message-ID: <9a8748490707041650s3b122007o46c8a34647b43af3@mail.gmail.com> (raw)
In-Reply-To: <20070704213420.GA5864@martell.zuzino.mipt.ru>
On 04/07/07, Alexey Dobriyan <adobriyan@gmail.com> wrote:
> 1) Drop __KERNEL__ out of profile.h. It contains only internal kernel stuff and
> not in exported headers list
Even if it's not in the list of exported headers, does it really hurt
to retain that extra safeguard?
> 2) Put profile.c under CONFIG_PROFILING. You enabled profiling in config, you
> will get it.
Makes logical sense. If the user didn't enable CONFIG_PROFILING why
should she get any profiling related overhead of any kind if we can
avoid it?
> Removes conditional branch from schedule(). Code savings on my
> usual config:
>
> text data bss dec hex filename
> 2921871 179895 180224 3281990 321446 vmlinux before
> 2920141 179847 180224 3280212 320d54 vmlinux after
> --------------------------------------------------------------
> -1730 -48 -1778
>
Nice savings there. Not that 1.7K is huge, but it's kernel memory is
precious :-)
> 3) Make timer_hook static (hi, Adrian!)
Makes perfect sense to me.
> 4) Convert do {} while (0) into static inline functions
Seems reasonable.
> 5) minor misc stuff
>
One tiny comment below.
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
>
> include/linux/profile.h | 78 +++++++++++++++++++++++++-----------------------
> kernel/Makefile | 3 +
> kernel/profile.c | 2 -
> 3 files changed, 44 insertions(+), 39 deletions(-)
>
[snip]
> +#define prof_on 0
> +static inline void profile_init(void)
> +{
> +}
Just to be pedantic; don't we want a blank line between functions
here, even if they are empty?
> +static inline void profile_tick(int type)
> +{
> +}
> +static inline void profile_hits(int type, void *ip, unsigned int nr_hits)
> +{
> +}
> +static inline void profile_hit(int type, void *ip)
> +{
> +}
> +static inline void profile_munmap(unsigned long addr)
> +{
> +}
> +static inline void profile_task_exit(struct task_struct *tsk)
> +{
> +}
> +static inline int profile_handoff_task(struct task_struct *tsk)
> +{
> + return 0;
> +}
[snip]
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2007-07-04 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 21:34 Alexey Dobriyan
2007-07-04 22:39 ` Andi Kleen
2007-07-04 23:50 ` Jesper Juhl [this message]
2007-07-05 10:16 ` Denis Vlasenko
2007-07-05 10:20 ` Robert P. J. Day
2007-07-06 21:18 ` Alexey Dobriyan
2007-07-08 18:51 ` Adrian Bunk
2007-07-08 18:53 ` Jesper Juhl
2007-07-10 12:43 ` Matt Mackall
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=9a8748490707041650s3b122007o46c8a34647b43af3@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--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®