All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Steffen Persvold <sp@scali.com>
Cc: Margit Schubert-While <margit@margit.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-rc2 strange L1 cache values
Date: Wed, 20 Nov 2002 19:29:15 +0000	[thread overview]
Message-ID: <20021120192915.GA14194@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0211202011291.15336-100000@sp-laptop.isdn.scali.no>

On Wed, Nov 20, 2002 at 08:23:04PM +0100, Steffen Persvold wrote:

 > The original poster reported on 2.4.20-rc2 (which reports 0K), not 2.4.18. 
 > The output I provided was from .18 and that clearly says 'L1 I cache:12K'.
 > Here are some 'sniplets' of my 2.4.18 dmesg :
 > CPU: L1 I cache: 12K, L1 D cache: 8K

My bad. Yes, earlier kernels did confuse the two.
the 12K actually means the trace cache holds 12,000 uops
rather than you have 12KB of cache.

The only bug is the reporting unit.

 > Ok, since this is now fixed (with your patch), I really don't care about 
 > earlier kernels anyway (however some of my customer might have if it was 
 > an issue). Do you know if your patch is going into 2.4.20 release (it's a 
 > rather small and useful patch) ?

I've resubmitted it to Marcelo, but it still didn't show up..

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-11-20 19:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-20 18:05 2.4.20-rc2 strange L1 cache values Margit Schubert-While
2002-11-20 18:13 ` Dave Jones
2002-11-20 18:48   ` Steffen Persvold
2002-11-20 19:01     ` Dave Jones
2002-11-20 19:23       ` Steffen Persvold
2002-11-20 19:29         ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-20 20:40 Margit Schubert-While
2002-11-20 21:38 ` Dave Jones

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=20021120192915.GA14194@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=margit@margit.com \
    --cc=sp@scali.com \
    /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.