From: Mathias Kretschmer <mathias@lemur.sytes.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: RE: PATCH: Recognize Tualatin cache size in 2.4.x
Date: Tue, 19 Nov 2002 20:41:26 -0500 [thread overview]
Message-ID: <3DDAE846.6080503@lemur.sytes.net> (raw)
> > I tested it in a Compaq Proliant 330ML-G2 (P3 1.4) and a kernel
> compilation is 100% faster if the patch is applied.
> <raises eyebrows>. The SMP weighting used by various parts of the
> kernel will be slightly off, but I'd be amazed if it made *that much*
> difference.
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.
Cheers,
Mathias
next reply other threads:[~2002-11-20 1:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 1:41 Mathias Kretschmer [this message]
2002-11-20 13:15 ` PATCH: Recognize Tualatin cache size in 2.4.x Dave Jones
2002-11-20 14:24 ` Mathias Kretschmer
-- 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=3DDAE846.6080503@lemur.sytes.net \
--to=mathias@lemur.sytes.net \
--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 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.