From: Dan Kegel <dank@kegel.com>
To: linux-kernel@vger.kernel.org
Cc: Will Cohen <wcohen@redhat.com>, Brandan C Lennox <brandan@bclennox.com>
Subject: re: function ordering (was: Re: [RFC] exit_thread() speedups in x86
Date: Mon, 04 Jul 2005 06:12:23 -0700 [thread overview]
Message-ID: <42C935B7.1050506@kegel.com> (raw)
Arjan van de Ven wrote:
> hmm. I wonder if a slightly different approach (based on the __slow)
> idea would make sense
> 1) Use -ffunction-sections option from gcc to put each function in it's
> own section
> 2) Use readprofile/oprofile data to collect an (external to the code)
> list of hot/cold functions (we can put a default list in the kernel
> source somewhere and allow people to measure their own if they want)
> 3) Use this list to make a linker script to order the functions
Somebody recently implemented something similar; see
http://www.bclennox.com/ldreorder/
It used valgrind rather than oprofile.
- Dan
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
reply other threads:[~2005-07-04 13:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42C935B7.1050506@kegel.com \
--to=dank@kegel.com \
--cc=brandan@bclennox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wcohen@redhat.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