From: Arjan van de Ven <arjan@infradead.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Adrian Bunk <bunk@stusta.de>
Subject: Re: [patch 2.6.13-rc3a] i386: inline restore_fpu
Date: Sat, 23 Jul 2005 13:46:31 -0400 [thread overview]
Message-ID: <1122140791.3582.25.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0507231033370.6074@g5.osdl.org>
On Sat, 2005-07-23 at 10:38 -0700, Linus Torvalds wrote:
> So maybe a few hints to the binutils people might just make them go: "try
> this patch/cmdline flag", and solve many more problems. They likely have a
> lot of this kind of code _already_, or have at least been thinking about
> it.
>
> I personally believe that there's likely a lot more to be had from code
> (and data) layout than there is from things like alias analysis or
> aggressive inlining.
for userland it's not that complex and exists already; basically gprof
has this analysis capability, and from that there's tooling (well I
wrote it and I'm sure others did too) to create a linker script
automatically to order things according to their gprof desired order.
This gprof based approach is taking actual runtime patterns into account
not just static callgraph analysis.
For the kernel the runtime measurement is obviously tricky (kgprof
anyone?) but the static analysis method really shouldn't be too hard.
(well I guess "optimal" will be NP complete, but "pretty damn close"
ought to be reasonable)
next prev parent reply other threads:[~2005-07-23 17:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 7:09 [patch 2.6.13-rc3a] i386: inline restore_fpu Chuck Ebbert
2005-07-23 17:38 ` Linus Torvalds
2005-07-23 17:46 ` Arjan van de Ven [this message]
2005-07-23 18:02 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2005-07-27 1:40 linux
2005-07-26 21:23 Chuck Ebbert
2005-07-26 21:47 ` Linus Torvalds
2005-07-26 21:23 Chuck Ebbert
2005-07-25 2:34 Kenneth Parrish
2005-07-24 12:56 Kenneth Parrish
[not found] <200507212309_MC3-1-A534-95EF@compuserve.com.suse.lists.linux.kernel>
[not found] ` <20050722132756.578acca7.akpm@osdl.org.suse.lists.linux.kernel>
2005-07-23 15:35 ` Andi Kleen
2005-07-23 7:09 Chuck Ebbert
2005-07-23 17:33 ` Linus Torvalds
2005-07-22 9:58 Chuck Ebbert
2005-07-22 3:06 Chuck Ebbert
2005-07-22 3:27 ` Andrew Morton
2005-07-22 5:22 ` Linus Torvalds
2005-07-22 11:23 ` Arjan van de Ven
2005-07-22 8:14 ` Adrian Bunk
2005-07-22 18:13 ` Linus Torvalds
2005-07-25 19:26 ` Bill Davidsen
2005-07-22 23:19 ` Linus Torvalds
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=1122140791.3582.25.camel@localhost.localdomain \
--to=arjan@infradead.org \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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