mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "BALBIR SINGH" <balbir.singh@wipro.com>
To: "lkml" <linux-kernel@vger.kernel.org>
Subject: Pentium IV cache line size
Date: Sun, 14 Jul 2002 13:57:26 +0530	[thread overview]
Message-ID: <009c01c22b10$4934e6b0$290806c0@wipro.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

Hello, All,

Dave Jones sent out a patch about Pentium IV cacheline sizes,
please refer to

http://marc.theaimsgroup.com/?l=linux-kernel&m=100297450316163&w=2

to which Manfred Spraul responded

http://marc.theaimsgroup.com/?l=linux-kernel&m=100299763026680&w=2

I think the patch is correct and should be applied.

>From Pentium IV, System Programming Guide, Section 9.1, Page 9-2,
Table 9-1. Order # 245472


L1 Data Cache - Pentium 4 and Intel Xeon processors: 8 KBytes, 4-way set
associative, 64-byte
cache line size.


L2 Unified Cache - Pentium 4 and Intel Xeon processors: 256 KBytes 8-way
set associative,
sectored, 64-byte cache line size.

The point is that according to the specs both L1 and L2 cacheline sizes
are 64-byte.

Comments,
Balbir


[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 490 bytes --]

**************************Disclaimer************************************

Information contained in this E-MAIL being proprietary to Wipro Limited is 
'privileged' and 'confidential' and intended for use only by the individual
 or entity to which it is addressed. You are notified that any use, copying 
or dissemination of the information contained in the E-MAIL in any manner 
whatsoever is strictly prohibited.

***************************************************************************

             reply	other threads:[~2002-07-14  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-14  8:27 BALBIR SINGH [this message]
2002-07-14 20:58 ` Mark Hahn
2002-07-17  0:53 Mikael Pettersson

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='009c01c22b10$4934e6b0$290806c0@wipro.com' \
    --to=balbir.singh@wipro.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

all inboxes | Powered by JetHome®