From: "David S. Miller" <davem@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: IOMMUs was Re: Intel vs AMD x86-64
Date: Tue, 24 Feb 2004 10:13:40 -0800 [thread overview]
Message-ID: <20040224101340.47341f28.davem@redhat.com> (raw)
In-Reply-To: <p73r7wk607c.fsf_-_@verdi.suse.de>
On 24 Feb 2004 15:06:47 +0100
Andi Kleen <ak@suse.de> wrote:
> One side effect of this is that the IOMMU TLB flush strategy is a bit
> dumb, because it has to do config space accesses for it.
This can be costly, but if you flush the IOMMU like sparc64 does (basically
it's similar to how KMAPs are flushed on x86), the cost gets real low because
then you only flush the whole iommu once every time you walk the whole mapping
table of the iommu.
I'm sure you've probably thought of this already, just mentioning it in case
you haven't.
next prev parent reply other threads:[~2004-02-24 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0402231625220.9708-100000@chimarrao.boston.redhat.com.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.58.0402231335430.3005@ppc970.osdl.org.suse.lists.linux.kernel>
[not found] ` <20040223134853.5947a414.davem@redhat.com.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.58.0402231359280.3005@ppc970.osdl.org.suse.lists.linux.kernel>
2004-02-24 14:06 ` IOMMUs was Re: Intel vs AMD x86-64 Andi Kleen
2004-02-24 18:13 ` David S. Miller [this message]
2004-02-27 1:28 ` Andi Kleen
2004-02-24 18:41 ` David S. Miller
2004-02-25 0:36 ` Benjamin Herrenschmidt
2004-02-24 15:50 richard.brunner
2004-02-24 16:27 ` Mike Fedyk
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=20040224101340.47341f28.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.