All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: Olof Johansson <olof@lixom.net>, linuxppc-dev@ozlabs.org
Subject: Re: [RFC]: map 4K iommu pages even on 64K largepage systems.
Date: Mon, 23 Oct 2006 17:50:35 -0700	[thread overview]
Message-ID: <453D635B.20405@am.sony.com> (raw)
In-Reply-To: <20061024002540.GA6360@austin.ibm.com>

Linas Vepstas wrote:
> Subject: [RFC]: map 4K iommu pages even on 64K largepage systems.
...
> Some experimentaiton indicates that this is essentially because
> one 1500 byte ethernet MTU gets mapped as a 64K DMA region when
> the large 64K pages are enabled. Thus, it doesn't take much to
> exhaust all of the available DMA mappings for a high-speed card.
> 
> This patch changes the iommu allocator to work with its own 
> unique, distinct page size. Although the patch is long, its
> actually quite simple: it just #defines  distinct IOMMU_PAGE_SIZE
> and then uses this in al the places tha matter.

This is a step in the right direction.  Cell allows each device to
have its own io pagesize, from among those that the io controller
supports (4k, 64k, 1m,16m).  This limitation of the current iommu
code that you try to address here has caused me to use platform
specific dma alloc routines.

-Geoff

  reply	other threads:[~2006-10-24  0:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24  0:25 [RFC]: map 4K iommu pages even on 64K largepage systems Linas Vepstas
2006-10-24  0:50 ` Geoff Levand [this message]
2006-10-24  2:23   ` Benjamin Herrenschmidt
2006-10-24  2:22 ` Benjamin Herrenschmidt
2006-10-24  3:00   ` Geoff Levand
2006-10-24  4:43 ` Benjamin Herrenschmidt
2006-10-24  5:14   ` [PATCH] powerpc: " Benjamin Herrenschmidt
2006-10-24 20:08     ` Linas Vepstas
2006-10-24 21:41       ` Benjamin Herrenschmidt
2006-10-24 23:17         ` Linas Vepstas

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=453D635B.20405@am.sony.com \
    --to=geoffrey.levand@am.sony.com \
    --cc=linas@austin.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    /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.