public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Stevie O <stevie@qrpff.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "Colo[u]rs"
Date: 10 Dec 2001 02:26:47 -0500	[thread overview]
Message-ID: <1007969208.1237.32.camel@phantasy> (raw)
In-Reply-To: <5.1.0.14.2.20011210020236.01cca428@whisper.qrpff.net>
In-Reply-To: <5.1.0.14.2.20011210020236.01cca428@whisper.qrpff.net>

On Mon, 2001-12-10 at 02:07, Stevie O wrote:
> After a few failed web searches (combos like 'linux cache color' just gave 
> me a bunch of references to video), I am resorting to this list for this 
> question.
> 
> What exactly do y'all mean by these "colors"? Task colors, cache colors, 
> and probably a few other colors i've missed/forgotten about. What do these 
> colors represent? How are they used to group tasks/cache entries? Is what 
> they're actually 

Cache color is how many indexes there are into a cache.  Caches
typically aren't direct mapped: they are indexed into cache lines by a
hash.  This means that certain memory values (of the 2^32 on your PC)
will map to the same cache line.  This means only one can be there at
the same time, and the newer one throws the old one out.

Coloring of data structures is down to give random offsets to data such
that they are not are multiples of the some value and thus don't map to
the same cache line.  This is what Linux's slab allocator is meant to
do.

	Robert Love


  reply	other threads:[~2001-12-10  7:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200112100656.fBA6ukA14374@www.hockin.org>
2001-12-10  7:07 ` "Colo[u]rs" Stevie O
2001-12-10  7:26   ` Robert Love [this message]
2001-12-10  7:36     ` "Colo[u]rs" Robert Love
2001-12-10  7:28   ` "Colo[u]rs" Larry McVoy
2001-12-10  7:21     ` "Colo[u]rs" David Lang
2001-12-10  7:51       ` "Colo[u]rs" Larry McVoy
2001-12-10  7:30         ` "Colo[u]rs" David Lang
2001-12-10  7:33   ` "Colo[u]rs" Stevie O
2001-12-10  8:37     ` "Colo[u]rs" Alan Cox
2001-12-10  8:00   ` "Colo[u]rs" Stevie O
2001-12-10  8:13     ` "Colo[u]rs" Robert Love
2001-12-10 12:22       ` "Colo[u]rs" ncw
2001-12-10 17:52         ` "Colo[u]rs" Chris Wedgwood

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=1007969208.1237.32.camel@phantasy \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stevie@qrpff.net \
    /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