From: <cutaway@bellsouth.net>
To: "Denis Vlasenko" <vda@ilport.com.ua>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] exit_thread() speedups in x86 process.c
Date: Sun, 3 Jul 2005 15:59:11 -0400 [thread overview]
Message-ID: <005801c58009$b1a13400$2800000a@pc365dualp2> (raw)
In-Reply-To: <200507021456.40667.vda@ilport.com.ua>
----- Original Message -----
From: "Denis Vlasenko" <vda@ilport.com.ua>
To: "Chuck Ebbert" <76306.1226@compuserve.com>; <cutaway@bellsouth.net>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>; "Coywolf Qi Hunt"
<coywolf@gmail.com>
Sent: Saturday, July 02, 2005 07:56
Subject: Re: [RFC] exit_thread() speedups in x86 process.c
>
> 80/20 rule says that 80% of code runs 20% of time,
> thus we need only __fast. Everything else will be by default __slow.
> (IOW: normal .text section is __slow, no need to add another one).
What makes you think __fast implies everything else should necessarily be
"slow"?
You might want to entertain the idea that some systems employ several
different speeds of memory where the penalty for making such assumptions
could be extreme if the bootstrap were to metric available memory regions
for response and locate portions of the system accordingly someday.
next prev parent reply other threads:[~2005-07-03 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 2:57 Chuck Ebbert
2005-07-02 11:56 ` Denis Vlasenko
2005-07-03 11:45 ` function ordering (was: Re: [RFC] exit_thread() speedups in x86 process.c) Arjan van de Ven
2005-07-03 12:30 ` Hugh Dickins
2005-07-03 12:48 ` Arjan van de Ven
2005-07-04 9:29 ` Christoph Hellwig
2005-07-04 10:28 ` Hugh Dickins
2005-07-03 19:59 ` cutaway [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-05 18:30 [RFC] exit_thread() speedups in x86 process.c William Cohen
[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 ` Andi Kleen
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='005801c58009$b1a13400$2800000a@pc365dualp2' \
--to=cutaway@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
/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®