From: Oliver Feiler <kiza@gmx.net>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon adv speculative caching fix removed from 2.4.20?
Date: Tue, 11 Feb 2003 02:16:52 +0100 [thread overview]
Message-ID: <200302110216.53111.kiza@gmx.net> (raw)
In-Reply-To: <p73fzqvbw6b.fsf@oldwotan.suse.de>
On Monday 10 February 2003 23:36, Andi Kleen wrote:
>
> The "long term" fix for it went in instead (arch/i386/mm/pageattr.c)
> The kernel is careful now to not create conflicting cache attributes
> for AGP and other mappings. This makes the linux kernel x86
> conformant in this area. It also increases performance on
> Athlon XP/MP because they can now use large pages in kernel space again.
Ah yes, indeed. I must have missed that. :)
Thanks for the quick answers everyone.
-Oliver
--
Oliver Feiler <kiza@(kcore.de|lionking.org|gmx(pro).net)>
http://kiza.kcore.de/ <-- homepage
PGP-key --> /pgpkey.shtml
http://kiza.kcore.de/journal/
next prev parent reply other threads:[~2003-02-11 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200302102321.30549.kiza@gmx.net.suse.lists.linux.kernel>
2003-02-10 22:36 ` Athlon adv speculative caching fix removed from 2.4.20? Andi Kleen
2003-02-11 1:16 ` Oliver Feiler [this message]
2003-02-10 22:21 Oliver Feiler
2003-02-10 22:22 ` 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=200302110216.53111.kiza@gmx.net \
--to=kiza@gmx.net \
--cc=ak@suse.de \
--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