From: Brian Gerst <bgerst@didntduck.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jimmie Mayfield <mayfield+kernel@sackheads.org>,
linux-kernel@vger.kernel.org
Subject: Re: Athlon fast_copy_page revisited
Date: Wed, 30 May 2001 15:06:33 -0400 [thread overview]
Message-ID: <3B1544B9.CE5F40DB@didntduck.org> (raw)
In-Reply-To: <E155AmZ-0006NL-00@the-village.bc.nu>
Alan Cox wrote:
>
> > schemes in user-space but if I try in kernel space, I get the notorious crash inside
> > fast_copy_page. (If there was some sort of fundamental hardware problem associated with
> > prefetch or streaming, wouldn't it also show up in user-space?) Note: I've yet to try the
>
> That has been one of the great puzzles. There are patterns that are very
> different in kernel space - notably physically linear memory and code running
> from a 4Mb tlb.
Have you tried hacking the kernel to only use 4k page tables (ie. filter
out the PSE capability bit)? A shot in the dark, but probably worth
trying.
--
Brian Gerst
next prev parent reply other threads:[~2001-05-30 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 18:08 Athlon fast_copy_page revisited Jimmie Mayfield
2001-05-30 18:33 ` Alan Cox
2001-05-30 19:06 ` Brian Gerst [this message]
[not found] <fa.f5i683v.igqsp3@ifi.uio.no>
2001-06-02 17:38 ` Gordon Sadler
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=3B1544B9.CE5F40DB@didntduck.org \
--to=bgerst@didntduck.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mayfield+kernel@sackheads.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