mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kumon@flab.fujitsu.co.jp
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	lkml <linux-kernel@vger.kernel.org>,
	Shuji YAMAMURA <yamamura@flab.fujitsu.co.jp>
Cc: kumon@flab.fujitsu.co.jp
Subject: Re: [PATCH] task_struct colouring ...
Date: Sun, 2 Dec 2001 08:50:50 +0900	[thread overview]
Message-ID: <200112012350.IAA03884@asami.proc.flab.fujitsu.co.jp> (raw)
In-Reply-To: <Pine.LNX.4.40.0112011350120.1696-100000@blue1.dev.mcafeelabs.com>
In-Reply-To: <E16A6lc-0006cV-00@the-village.bc.nu> <Pine.LNX.4.40.0112011350120.1696-100000@blue1.dev.mcafeelabs.com>

Davide Libenzi writes:
 > On Sat, 1 Dec 2001, Alan Cox wrote:
 > > Because it is much much much faster
 > 
 > We'll see how much faster is the global register allocation against code
 > like :
 > 
 > movl %esp, %eax
 > andl $-8192, %eax
 > movl (%eax), %eax

Current should be much faster, if it is accessed very frequently.
If the frequency is high, the value is very likely being kept on L1
cache. If that's true, the access time is fast enough.
So, using indirection doesn't cause large penalty.

Apart from that, stack coloring is difficult. Recent CPUs use much
larger cache block, coloring needs big room in the stack area.
Pentium4 is said using 64B block, but actually it is sectored cache
within 128B block.
1KB room for stack coloring realizes only 8 colors.
--
Kouichi Kumon, Software Laboratory, Fujitsu Labs.
kumon@flab.fujitsu.co.jp

  parent reply	other threads:[~2001-12-01 23:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-30 21:47 Davide Libenzi
2001-11-30 22:40 ` Alan Cox
2001-11-30 23:37   ` H. Peter Anvin
2001-11-30 23:53   ` Davide Libenzi
2001-11-30 23:57     ` Alan Cox
2001-12-01  0:33       ` Davide Libenzi
2001-12-01  1:05         ` H. Peter Anvin
2001-12-01  1:30           ` Davide Libenzi
2001-12-01  1:24             ` H. Peter Anvin
2001-12-01  1:41               ` Davide Libenzi
2001-12-01  1:36                 ` H. Peter Anvin
2001-12-01  9:58               ` Alan Cox
2001-12-01  9:49         ` Alan Cox
2001-12-01 23:37           ` Davide Libenzi
2001-12-02  0:02             ` [MOc]cda*mirabilos
2001-12-02  0:56               ` Davide Libenzi
2001-12-02 15:06                 ` [MOc]cda*mirabilos
2001-12-02 19:49                   ` Davide Libenzi
2001-12-02 19:50                     ` Thorsten Glaser
2001-12-01 23:50           ` kumon [this message]
2001-12-02  0:11             ` Davide Libenzi
2001-12-02 16:39               ` Alan Cox
2001-12-01 10:17 Manfred Spraul
2001-12-01 21:49 ` Davide Libenzi
2001-12-01 22:04 ` H. Peter Anvin

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=200112012350.IAA03884@asami.proc.flab.fujitsu.co.jp \
    --to=kumon@flab.fujitsu.co.jp \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yamamura@flab.fujitsu.co.jp \
    /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®