Re: [RFC] exit_thread() speedups in x86 process.c

[<cutaway@bellsouth.net>]

FWIW Chuck, this is precisely how OS/2 Warp 3 got page tuned when I was with
IBM Boca many years ago.  The compilers got tweaked to be able to emit
function code to different text sections and a massive system wide code
triage was undertaken based on "common usage scenario" profiling run data
from the perf analysis group.  The results spoke for themselves compared to
the previous 2.X releases - this plan can work and pay off very well.  It
DID worked and paid off very well.


----- Original Message ----- 
From: "Chuck Ebbert" <76306.1226@compuserve.com>
To: "Denis Vlasenko" <vda@ilport.com.ua>
Cc: <cutaway@bellsouth.net>; "Coywolf Qi Hunt" <coywolf@gmail.com>;
"linux-kernel" <linux-kernel@vger.kernel.org>
Sent: Wednesday, June 22, 2005 01:48
Subject: Re: [RFC] exit_thread() speedups in x86 process.c


>
>   And doing this manually is trivial:
>
>         1. Add two sections to vmlinux.lds.S: .fast.text and .slow.text
>         2. Define __fast __attribute__(__section__(".fast.text"))
>         3. Define __slow similarly
>         4. Start tagging functions with __fast and __slow as needed
>
>   Very little work for much potential gain, AFAICS.
>
>
> --
> Chuck

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/