From: William Cohen <wcohen@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] exit_thread() speedups in x86 process.c
Date: Tue, 05 Jul 2005 14:30:55 -0400 [thread overview]
Message-ID: <42CAD1DF.3030405@redhat.com> (raw)
One of the difficulties function reordering is getting useful data to
figure out a reasonable order for the functions. People do guess wrong
on the frequency of particular functions. Also naive ordering techniques
like just ordering functions based on frequency do not work well.
A North Carolina State University senior project was done to generate
ordering to improve TLB and cache hit ratios using the information
generated by valgrind for user-space programs:
http://www.bclennox.com/cgi-bin/show.cgi?page=home
Xen is running the domains (and kernels) in user-space. Would it be
possible to adapt valgrind/xen to run a domain so that similar
information could be collected about a particular kernel? Being able to
use valgrind on the kernel could allow other analysis of the kernel
code, e.g. find unwanted TLB flushes.
-Will
I am not subscribed to the list, so please cc me on responses.
next reply other threads:[~2005-07-05 18:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 18:30 William Cohen [this message]
[not found] <200507012258_MC3-1-A340-3A81@compuserve.com.suse.lists.linux.kernel>
[not found] ` <200507021456.40667.vda@ilport.com.ua.suse.lists.linux.kernel>
2005-07-03 16:05 ` [RFC] exit_thread() speedups in x86 process.c Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-07-02 2:57 Chuck Ebbert
2005-07-02 11:56 ` Denis Vlasenko
2005-07-03 19:59 ` cutaway
2005-06-22 5:48 Chuck Ebbert
2005-06-22 8:41 ` cutaway
2005-06-14 1:16 cutaway
2005-06-14 3:08 ` Coywolf Qi Hunt
2005-06-14 4:26 ` cutaway
2005-06-14 7:43 ` Denis Vlasenko
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=42CAD1DF.3030405@redhat.com \
--to=wcohen@redhat.com \
--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