mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "saeed bishara" <saeed.bishara@gmail.com>
To: "Paolo Ornati" <ornati@fastwebnet.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: add new code section for kernel code
Date: Thu, 6 Apr 2006 18:27:43 +0300	[thread overview]
Message-ID: <c70ff3ad0604060827m6c286965p5a92374347a8a1f0@mail.gmail.com> (raw)
In-Reply-To: <20060406151003.0ef4e637@localhost>

very cooooooooool!!
regarding the readprofile, I think it's recommended to mention that
functions called within spinlocks won't show up.


On 4/6/06, Paolo Ornati <ornati@fastwebnet.it> wrote:
> On Thu, 6 Apr 2006 15:45:47 +0300
> "saeed bishara" <saeed.bishara@gmail.com> wrote:
>
> >  I'm developing linux kernel for ARM cpu with direct-mapped
> > instruction cache, sometimes I notice that the pefromance of the
> > kernel (for some test) is highly dependent on the code layout, in
> > order to fix that I added new code section, and for each kernel
> > function that highly invokerd I added compiler attribute so it will
> > allocated in that section (exactly as the __init section)
>
> It's already done in 2.6.17-rc1 for x86_64:
>
> Processor type and feature --> Function reordering
>
> arch/x86_64/Kconfig:
>
> config REORDER
>         bool "Function reordering"
>         default n
>         help
>          This option enables the toolchain to reorder functions for a more
>          optimal TLB usage. If you have pretty much any version of binutils,
>          this can increase your kernel build time by roughly one minute.
>
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4bdc3b7f1b730c07f5a6ccca77ee68e044036ffc
>
> --
>         Paolo Ornati
>         Linux 2.6.16.1 on x86_64
>

  reply	other threads:[~2006-04-06 15:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06 12:45 saeed bishara
2006-04-06 13:10 ` Paolo Ornati
2006-04-06 15:27   ` saeed bishara [this message]
2006-04-06 16:47   ` saeed bishara
2006-04-07 11:02     ` saeed bishara
2006-04-07 15:14       ` Arjan van de Ven
2006-04-07 15:43         ` Russell King
2006-04-09  9:53           ` saeed bishara
2006-04-09 20:30             ` Russell King
2006-04-10  7:11               ` saeed bishara
2006-04-10  9:12               ` Dimitry Andric
2006-04-11 14:49                 ` saeed bishara
2006-04-12  5:34                   ` Arjan van de Ven

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=c70ff3ad0604060827m6c286965p5a92374347a8a1f0@mail.gmail.com \
    --to=saeed.bishara@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ornati@fastwebnet.it \
    /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®