mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: davidm@hpl.hp.com, Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org, davidm@napali.hpl.hp.com
Subject: Re: adjust prefetch in free_one_pgd()
Date: Fri, 2 Aug 2002 09:53:46 -0700	[thread overview]
Message-ID: <15690.47386.247705.533190@napali.hpl.hp.com> (raw)
In-Reply-To: <1028311133.18317.96.camel@irongate.swansea.linux.org.uk>

>>>>> On 02 Aug 2002 18:58:53 +0100, Alan Cox <alan@lxorguk.ukuu.org.uk> said:

  >>  Cacheable and side-effects don't go together.  Even without
  >> explicit software prefetches, most modern CPUs will happily and
  >> aggressively prefetch stuff from cacheable translations.

  Alan> Yes we got burned on that with the latest AMD processors. They
  Alan> prefetch into an area we accidentally have marked with
  Alan> differing cachabilities between kernel and user space when
  Alan> using the nv binary driver stuff (but its our bug not
  Alan> theirs). There's a horrid hack in 2.4.19rc to deal with it
  Alan> pending merging the proper patches

Yes, I'm well aware of this issue as ia64 has basically the same setup
in this regard.  For ia64, it seems to be acceptable to require
that AGP DMA operates in coherent mode, so that all the memory can be
mapped cacheable.  With old chipsets, coherent AGP DMA is slow, but
with more recent chipsets (including hp's zx1), there won't be a
performance penalty.  I realize that this isn't a solution for x86 as
there is too much of an installed base.

	--david

  reply	other threads:[~2002-08-02 16:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02  0:12 David Mosberger
2002-08-02 13:04 ` Alan Cox
2002-08-02 15:39   ` David Mosberger
2002-08-02 15:46     ` Linus Torvalds
2002-08-02 15:56       ` Dave Jones
2002-08-02 15:59         ` Linus Torvalds
2002-08-02 16:04           ` Dave Jones
2002-08-02 17:49       ` Alan Cox
2002-08-02 16:38         ` David Mosberger
2002-08-02 17:58           ` Alan Cox
2002-08-02 16:53             ` David Mosberger [this message]
2002-08-03 16:59       ` David Woodhouse
2002-08-03 17:22         ` Linus Torvalds
2002-08-03 17:39           ` David Woodhouse
2002-08-03 19:36             ` Linus Torvalds
2002-08-03 22:03               ` David Woodhouse
2002-08-03 22:40                 ` Linus Torvalds

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=15690.47386.247705.533190@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®