mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] pageattr update
Date: Thu, 13 Jun 2002 08:09:32 -0700	[thread overview]
Message-ID: <15624.46508.257287.233406@napali.hpl.hp.com> (raw)
In-Reply-To: <20020613061246.A7121@redhat.com>

Hi Ben,

I'm have a concern about the current change_page_attr() patch.  It
gives the impression that the GART memory always gets mapped
write-combined.  This is not always true.  For example, on IA-64,
attribute-aliasing issues are prevented by requiring IA-64 platforms
to use coherent AGP DMA.  In other words, the AGP memory will be
mapped writeback, as usual.

As long as change_page_attr() is used for AGP-related stuff only,
there is probably no real issue with the patch in its current form
(its simply a no-op on most non-x86 platforms).  However, I'm a bit
worried that someone might start to use it for other things, such that
change_page_attr() could no longer be a no-op on those platforms.
Since the DMA coherency issue is an AGP specific issue, perhaps just
renaming the macro to agp_change_page_attr() would take care of my
concern.  What do you think?

	--david

  reply	other threads:[~2002-06-13 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-12  5:04 Benjamin LaHaise
2002-06-12 22:52 ` Andi Kleen
2002-06-13 10:12   ` Benjamin LaHaise
2002-06-13 15:09     ` David Mosberger [this message]
     [not found] <20020612010443.B1350@redhat.com.suse.lists.linux.kernel>
     [not found] ` <20020613005238.A17700@averell.suse.lists.linux.kernel>
     [not found]   ` <20020613061246.A7121@redhat.com.suse.lists.linux.kernel>
     [not found]     ` <15624.46508.257287.233406@napali.hpl.hp.com.suse.lists.linux.kernel>
2002-06-13 16:13       ` Andi Kleen

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=15624.46508.257287.233406@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=bcrl@redhat.com \
    --cc=davidm@hpl.hp.com \
    --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

all inboxes | Powered by JetHome®