From: "David S. Miller" <davem@redhat.com>
To: thunder@ngforever.de
Cc: linux-kernel@vger.kernel.org, zippel@linux-m68k.org,
ultralinux@vger.kernel.org
Subject: Re: L1_CACHE_SHIFT on sparc64
Date: Fri, 12 Jul 2002 14:55:24 -0700 (PDT) [thread overview]
Message-ID: <20020712.145524.91314408.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207121553230.3421-100000@hawkeye.luckynet.adm>
From: Thunder from the hill <thunder@ngforever.de>
Date: Fri, 12 Jul 2002 15:58:28 -0600 (MDT)
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?
Right. But who needs L1_CACHE_SHIFT? Nothing generic should
reference it. Did something get added to 2.5.x that needs it now?
I wouldn't have noticed yet as I've been away for nearly half a month
on vaction until a day or two ago.
next prev parent reply other threads:[~2002-07-12 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 21:58 Thunder from the hill
2002-07-12 21:55 ` David S. Miller [this message]
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=20020712.145524.91314408.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@ngforever.de \
--cc=ultralinux@vger.kernel.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®