public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: gallir@uib.es, linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: PATCH: Recognize Tualatin cache size in 2.4.x
Date: Wed, 20 Nov 2002 22:53:36 +0100	[thread overview]
Message-ID: <20021120225336.4e5beac6.skraw@ithnet.com> (raw)
In-Reply-To: <20021120214104.GA21030@suse.de>

On Wed, 20 Nov 2002 21:41:04 +0000
Dave Jones <davej@codemonkey.org.uk> wrote:

> On Wed, Nov 20, 2002 at 09:03:57PM +0100, Stephan von Krawczynski wrote:
>  > On Tue, 19 Nov 2002 12:08:34 +0000
>  > Dave Jones <davej@codemonkey.org.uk> wrote:
>  > 
>  > > On Mon, Nov 18, 2002 at 09:54:52PM +0100, Ricardo Galli wrote:
>  > > 
>  > >  > It's very cosmetic but very annoying for P3 > 1GHz, where Linux <= 2.4.20-preX 
>  > >  > only reports 32 KB of cache and it also seems to ignore the "cachesize" 
>  > >  > parameter. Perhaps it really uses 256KB, but not sure.
>  > > 
>  > > There was a bug related to that parameter, I'm sure if the fix
>  > > went into the same patch, or a separate one. I'll check later.
>  > 
>  > Sorry for this possibly dumb comment/question:
>  > my Tualatins have 512KB cache on die. Are we all sure that it's used?
>  > /proc says indeed 32KB on 2.4.20-rc2
> 
> Odd. If you can send me the output of dmesg, /proc/cpuinfo
> and x86info -a, I'll take a look.
> (You can find x86info at
>  http://www.codemonkey.org.uk/x86info/x86info-1.11.tar.gz)

Hi Dave,

I just tested your descriptors.diff, and here are the results:
(make dep clean bzImage modules modules_install, all same tree of course)

2.4.20-rc2:
real  5m27.670s   user  5m6.450s   sys  0m18.710s
real  5m27.590s   user  5m6.760s   sys  0m18.660s
real  5m27.953s   user  5m6.900s   sys  0m18.310s

2.4.20-rc2 with descriptors.diff:

real  5m29.005s   user  5m8.540s   sys  0m18.610s
real  5m27.752s   user  5m8.760s   sys  0m17.870s
real  5m29.021s   user  5m8.210s   sys  0m18.540s

Doesn't really look more than cosmetic, does it?
/proc output is correct with your diff.

Regards,
Stephan


  reply	other threads:[~2002-11-20 21:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-17 15:55 PATCH: Recognize Tualatin cache size in 2.4.x Ricardo Galli
2002-11-18 19:02 ` Dave Jones
2002-11-18 20:54   ` Ricardo Galli
2002-11-19 12:08     ` Dave Jones
2002-11-20 20:03       ` Stephan von Krawczynski
2002-11-20 20:22         ` erich
2002-11-20 21:41         ` Dave Jones
2002-11-20 21:53           ` Stephan von Krawczynski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-20  1:41 Mathias Kretschmer
2002-11-20 13:15 ` Dave Jones
2002-11-20 14:24   ` Mathias Kretschmer

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=20021120225336.4e5beac6.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=davej@codemonkey.org.uk \
    --cc=gallir@uib.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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