public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] task_struct colouring ...
Date: 30 Nov 2001 17:05:20 -0800	[thread overview]
Message-ID: <9u9acg$rrl$1@cesium.transmeta.com> (raw)
In-Reply-To: <E169xWr-0005EM-00@the-village.bc.nu> <Pine.LNX.4.40.0111301614000.1600-100000@blue1.dev.mcafeelabs.com>

Followup to:  <Pine.LNX.4.40.0111301614000.1600-100000@blue1.dev.mcafeelabs.com>
By author:    Davide Libenzi <davidel@xmailserver.org>
In newsgroup: linux.dev.kernel
> 
> The point is why store kernel pointers in global registers when You can
> achieve the same functionality, with a smaller patch, that does not need
> to be recoded for each CPU, without using global registers.
> 

Because global registers are faster!  This is exactly the kind of
stuff that is properly CPU-dependent and should be treated as such.
Heck, it even depends on what kind of multiprocessor architecture, if
any, you're using!

That being said, I belive that on most, if not all, processors, the
idea of having the pointer point not to "current" but to a per-CPU
memory area is *very* appealing, and a change that should be made
uniform unless it's a significant lose on some machines...

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2001-12-01  1:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-30 21:47 [PATCH] task_struct colouring 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 [this message]
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-01 23:50             ` kumon
2001-12-02  0:11               ` Davide Libenzi
2001-12-02 16:39                 ` Alan Cox
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
  -- strict thread matches above, loose matches on Subject: below --
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='9u9acg$rrl$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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