Linux IA64 platform development
 help / color / mirror / Atom feed
From: Russ Anderson <rja@efs.americas.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 1/6] align kenrel rbs on 128 byte
Date: Tue, 31 Jan 2006 15:26:05 +0000	[thread overview]
Message-ID: <200601311526.k0VFQ5FB907159@efs.americas.sgi.com> (raw)
In-Reply-To: <200601310848.k0V8mbg11087@unix-os.sc.intel.com>

Kenneth Chen wrote:
> Keith Owens wrote on Tuesday, January 31, 2006 12:57 AM
> > 
> > The cache lines are not guaranteed to be 128 byte aligned, they
> > were 64 on bigsur.  Change 127 to (L1_CACHE_BYTES - 1).
> 
> That did cross my mind and L1_CACHE_BYTES is such a misleading
> name.  In my head, L1 means the cache level closest to the CPU
> core, but here it appears to represent last level cache line.
> Do we have the numbering scheme reversed?  I have no idea what's
> going on here. 

I agree that L1_CACHE_BYTES is misleading.  Looking at
the usage, most (if not all) references expect the 
last (external/FSB) cache line size, not caches closer
to the core.  As Jes points out SMP_CACHE_BYTES is
more what they mean.

Why not just call it CACHE_BYTES, meaning the last cache
level.  Handling of caches closer to the core most likely
should be through PAL, or, it really needed, use the 
engineering cache level prefix.

-- 
Russ Anderson, OS RAS/Partitioning Project Lead  
SGI - Silicon Graphics Inc          rja@sgi.com

  parent reply	other threads:[~2006-01-31 15:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31  8:48 [patch 1/6] align kenrel rbs on 128 byte Chen, Kenneth W
2006-01-31  8:57 ` Keith Owens
2006-01-31  9:42 ` Chen, Kenneth W
2006-01-31 10:15 ` Andreas Schwab
2006-01-31 11:00 ` Jes Sorensen
2006-01-31 15:26 ` Russ Anderson [this message]
2006-01-31 16:25 ` Chen, Kenneth W
2006-01-31 19:58 ` Richard Harke
2006-01-31 19:59 ` Chen, Kenneth W
2006-01-31 20:16 ` Richard Harke

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=200601311526.k0VFQ5FB907159@efs.americas.sgi.com \
    --to=rja@efs.americas.sgi.com \
    --cc=linux-ia64@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