From: Con Kolivas <kernel@kolivas.org>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: linux list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
ck list <ck@vds.kolivas.org>
Subject: Re: [PATCH][2/4] sched: add discrete weighted cpu load function
Date: Wed, 15 Mar 2006 09:50:40 +1100 [thread overview]
Message-ID: <200603150950.40677.kernel@kolivas.org> (raw)
In-Reply-To: <44174791.7090905@bigpond.net.au>
On Wednesday 15 March 2006 09:45, Peter Williams wrote:
> Con Kolivas wrote:
> > I haven't checked but gcc may well inline weighted_cpuload anyway?
>
> It may be doing so for internal uses inside sched.c but I'm pretty sure
> that it won't for external calls.
Hmm I investigated briefly and only C99 inlining (whatever that means) will
allow me to locally inline and export as well. It would do so if I specified
-finline-functions which is not our default at all in the kernel (we only
recently disable -fnoinline-functions I believe). Anyway checking positively
shows me this on gcc 4.1.0:
0xc0111283 <find_busiest_queue+83>: call 0xc0110dc0 <weighted_cpuload>
So no, it doesn't get inlined.
> > The way you're suggesting adds a function that is never used by anything
> > but swap prefetch which would then need to be 'ifdef'ed out to not be
> > needlessly built on every system. Adding ifdefs is frowned upon already,
> > and to have an mm/ specific ifdef in sched.c would be rather ugly.
>
> Sometimes ugliness is the best option.
I spent quite some time trying to find the least cost way to do this without
uglifying code. I don't feel strongly about just how to do it though.
Comments from Andrew and Ingo would be most welcome on this matter.
Cheers,
Con
prev parent reply other threads:[~2006-03-14 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 8:06 [PATCH][2/4] sched: add discrete weighted cpu load function Con Kolivas
2006-03-13 9:06 ` Ingo Molnar
2006-03-13 9:14 ` Con Kolivas
2006-03-13 22:39 ` Peter Williams
2006-03-13 22:52 ` Con Kolivas
2006-03-13 23:16 ` Peter Williams
2006-03-14 22:09 ` Peter Williams
2006-03-14 22:26 ` Con Kolivas
2006-03-14 22:45 ` Peter Williams
2006-03-14 22:50 ` Con Kolivas [this message]
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=200603150950.40677.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pwil3058@bigpond.net.au \
/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