mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Grant Grundler" <grundler@google.com>
To: "FUJITA Tomonori" <fujita.tomonori@lab.ntt.co.jp>
Cc: James.Bottomley@hansenpartnership.com,
	linux-kernel@vger.kernel.org, mgross@linux.intel.com,
	linux-scsi@vger.kernel.org,
	"Alex Williamson" <alex.williamson@hp.com>,
	"Bjorn Helgaas" <bjorn.helgaas@hp.com>
Subject: Re: Intel IOMMU (and IOMMU for Virtualization) performances
Date: Thu, 5 Jun 2008 22:48:13 -0700	[thread overview]
Message-ID: <da824cf30806052248h3ac4ff21ocada15c376b399af@mail.gmail.com> (raw)
In-Reply-To: <20080606133955B.fujita.tomonori@lab.ntt.co.jp>

On Thu, Jun 5, 2008 at 9:44 PM, FUJITA Tomonori
<fujita.tomonori@lab.ntt.co.jp> wrote:
...
> The current Intel IOMMU scheme is a bit unbalanced. It invalidates the
> translation table every time dma_unmap_* is called, but it does the
> batching of the TLB flushes. But it's what the most of Linux's IOMMU
> code does.
>
> I think that only PARISC (and IA64, of course) IOMMUs do the batching
> of invalidating the translation table entries.

1/2 correct. PARISC and IA64 could be the same in this regard but are not.
See where sba_mark_invalid() is called in the respective sba_iommu.c.
PARISC invalidates the IO Pdir entry immediately but batches the
IO TLB shootdown and resource "free". IA64 could (and probably should)
do the same. Added Alex Williamson and Bjorn Helgaas to CC list.
Not an urgent issue though unless they are doing perf measurements
with SSDs or other block device with equivalent IOPS.

Since parisc-linux is unlikely to ever run VM's and the IOMMU has a
very limited number of IO TLB entries (8 or 16 about), I'm thinking the
batching is a waste of time and parisc should follow SPARC behavior.
I'll chat more with jejb/kyle/willy about it sometime.

thanks,
grant

  reply	other threads:[~2008-06-06  5:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 14:47 FUJITA Tomonori
2008-06-04 16:56 ` Andi Kleen
2008-06-05 14:49   ` FUJITA Tomonori
2008-06-04 18:06 ` Grant Grundler
2008-06-05 14:49   ` FUJITA Tomonori
2008-06-05 18:34     ` Grant Grundler
2008-06-05 19:01       ` James Bottomley
2008-06-06  4:44         ` FUJITA Tomonori
2008-06-06  5:48           ` Grant Grundler [this message]
2008-06-09  9:36             ` FUJITA Tomonori
2008-06-06 20:23     ` Muli Ben-Yehuda
2008-06-06 20:21   ` Muli Ben-Yehuda
2008-06-06 21:28     ` Grant Grundler
2008-06-06 21:36       ` Muli Ben-Yehuda
2008-06-06 21:51         ` Grant Grundler
2008-06-09  8:17           ` Andi Kleen
2008-06-09  9:36             ` FUJITA Tomonori
2008-06-09 10:20               ` Andi Kleen
2008-06-05 22:02 ` mark gross
2008-06-06  4:44   ` FUJITA Tomonori
2008-06-23 17:54     ` mark gross

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=da824cf30806052248h3ac4ff21ocada15c376b399af@mail.gmail.com \
    --to=grundler@google.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=alex.williamson@hp.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mgross@linux.intel.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®