public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul Rolland" <rol@as2917.net>
To: "'Dave Jones'" <davej@codemonkey.org.uk>
Cc: "'Juha Poutiainen'" <pode@iki.fi>, <linux-kernel@vger.kernel.org>
Subject: Re: L2 cache detection in Celeron 2GHz (P4 based)
Date: Wed, 19 Mar 2003 17:53:13 +0100	[thread overview]
Message-ID: <013d01c2ee38$0812e330$6100a8c0@witbe> (raw)
In-Reply-To: <20030319135841.GC28770@suse.de>

Hello,

>  > You can also add that the L1 detection doesn't seem to be correct
>  > either : 
>  > 0K Instruction cache, and 8K data cache for L1... This is not much
>  > for instruction, it seems it should be 12K...
> 
> That should be fixed in recent 2.4s (and not-so-recent 2.5s).
> What version are you seeing this problem on?

Quite a recent one : 2.4.20.

Here are the traces :

bash-2.05$ dmesg | grep -i L1 
CPU: L1 I cache: 0K, L1 D cache: 8K
CPU: L1 I cache: 0K, L1 D cache: 8K
bash-2.05$ uname -a
Linux addx-01.PAR 2.4.20-watchdog #4 SMP Mon Mar 17 10:57:00 GMT 2003
i686 unknown

bash-2.05$ cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Celeron(R) CPU 2.00GHz
stepping        : 7
cpu MHz         : 2000.356
cache size      : 8 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips        : 3984.58

Regards,
Paul



  reply	other threads:[~2003-03-19 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19  6:47 L2 cache detection in Celeron 2GHz (P4 based) Juha Poutiainen
2003-03-19  8:18 ` Paul Rolland
2003-03-19 13:58   ` Dave Jones
2003-03-19 16:53     ` Paul Rolland [this message]
2003-03-19 17:01       ` Dave Jones
2003-03-19 13:53 ` Dave Jones
2003-03-19 17:53   ` Juha Poutiainen

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='013d01c2ee38$0812e330$6100a8c0@witbe' \
    --to=rol@as2917.net \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pode@iki.fi \
    /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