From: Mathias Kretschmer <mathias@lemur.sytes.net>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Recognize Tualatin cache size in 2.4.x
Date: Wed, 20 Nov 2002 09:24:35 -0500 [thread overview]
Message-ID: <3DDB9B23.9030001@lemur.sytes.net> (raw)
In-Reply-To: 20021120131502.GA1768@suse.de
Dave Jones wrote:
> On Tue, Nov 19, 2002 at 08:41:26PM -0500, Mathias Kretschmer wrote:
> > I just patched my 2.4.20rc2 kernel. Now, it reports
> > 512K cache for my 2 Tualatin 1.26 GHz CPUs.
> >
> > 'time make -j4 bzImage' went down from 3:30 to 3:04.
> > Not too bad.
>
> That is quite an impressive gain. The patch I sent Marcelo which
> also fixes up a problem with some tualatins and adds P4 trace cache
> support is at..
>
> ftp.kernel.org/pub/linux/kernel/people/davej/patches/2.4/2.4.20/descriptors.diff
>
> As you have tualatins can you try with the above patch and make sure
> theres no regressions there ?
Hi Dave,
Here are the results. I've upgraded to gcc-3.2.1 yesterday evening.
Hence, we can not compare to the results from yesterday.
The ones below are new:
2.4.20rc2+small-patch (ran it three times with very similar results):
265.05user 16.66system 2:43.09elapsed 172%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (621129major+1391627minor)pagefaults 0swaps
2.4.20rc2-descriptors.diff (also run three times):
302.60user 16.95system 2:43.39elapsed 195%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (621129major+1390848minor)pagefaults 0swaps
Pretty much the same result - within the tolerance.
%CPU is up quite a bit.
Also, my optimization options are '-Os -march=pentium3'.
The machine was idle but still in multi-user mode. If
you need more precise results, I could do that over the weekend.
Cheers,
Mathias
---
> cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 11
model name : Intel(R) Pentium(R) III CPU family 1266MHz
stepping : 1
cpu MHz : 1280.932
cache size : 512 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 mmx fxsr sse
bogomips : 2555.90
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 11
model name : Intel(R) Pentium(R) III CPU family 1266MHz
stepping : 1
cpu MHz : 1280.932
cache size : 512 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 mmx fxsr sse
bogomips : 2555.90
next prev parent reply other threads:[~2002-11-20 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 1:41 PATCH: Recognize Tualatin cache size in 2.4.x Mathias Kretschmer
2002-11-20 13:15 ` Dave Jones
2002-11-20 14:24 ` Mathias Kretschmer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-17 15:55 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
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=3DDB9B23.9030001@lemur.sytes.net \
--to=mathias@lemur.sytes.net \
--cc=davej@codemonkey.org.uk \
--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