All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thunder from the hill <thunder@ngforever.de>
To: ultralinux@vger.kernel.org
Subject: L1_CACHE_SHIFT on sparc64
Date: Fri, 12 Jul 2002 21:58:28 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-102651120507229@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-102651148307513@msgid-missing>

Hi,

What is the proper value for L1_CACHE_SHIFT on sparc64?
The cache itself is two chunks of 16 bytes each, makes up 32 bytes. On 
i386, L1_CACHE_BYTES = (1 << L1_CACHE_SHIFT), so if this applies here, 
too, we have a L1_CACHE_SHIFT of... 5?

							Regards,
							Thunder
-- 
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o?  K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y- 
------END GEEK CODE BLOCK------


  reply	other threads:[~2002-07-12 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12 21:55 L1_CACHE_SHIFT on sparc64 David S. Miller
2002-07-12 21:58 ` Thunder from the hill [this message]
2002-07-12 22:14 ` Thunder from the hill
  -- strict thread matches above, loose matches on Subject: below --
2002-07-12 21:58 Thunder from the hill
2002-07-12 21:55 ` David S. Miller
2002-07-12 22:14   ` Thunder from the hill

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=marc-linux-ultrasparc-102651120507229@msgid-missing \
    --to=thunder@ngforever.de \
    --cc=ultralinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.