All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, alexisb@us.ibm.com, mingo@elte.hu,
	akpm@linux-foundation.org
Subject: Re: [PATCH -mm] x86 calgary: fix handling of devces that aren't behind the Calgary
Date: Tue, 3 Jun 2008 08:21:46 +0300	[thread overview]
Message-ID: <20080603052146.GI7011@il.ibm.com> (raw)
In-Reply-To: <20080531133114P.tomof@acm.org>

On Sat, May 31, 2008 at 01:31:33PM +0900, FUJITA Tomonori wrote:

> The calgary code can give drivers addresses above 4GB which is very
> bad for hardware that is only 32bit DMA addressable:
> 
> http://lkml.org/lkml/2008/5/8/423
> 
> This patch tries to fix the problem by using per-device
> dma_mapping_ops support. This fixes the calgary code to use swiotlb
> or nommu properly for devices which are not behind the
> Calgary/CalIOC2.
> 
> With this patch, the calgary code sets the global dma_ops to swiotlb
> or nommu, and the dma_ops of devices behind the Calgary/CalIOC2 to
> calgary_dma_ops. So the calgary code can handle devices safely that
> aren't behind the Calgary/CalIOC2.

This seems a little backward to me. I thought we were going to get rid
of the global dma_ops? If not, assuming going through the global one
would be more efficient, Calgary should be the global one and
nommu/swiotlb should be used on devices that do not have translation
enabled. The reason why is that the majority of devices on a Calgary
system, assuming Calgary is in use, will have translation enabled.

In general the patch looks good, barring the point above. We'll give
it a spin on some Calgary/CalIOC2 machines.

Cheers,
Muli



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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31  4:31 [PATCH -mm] x86 calgary: fix handling of devces that aren't behind the Calgary FUJITA Tomonori
2008-06-03  5:21 ` Muli Ben-Yehuda [this message]
2008-06-03  6:43   ` FUJITA Tomonori
2008-06-03 16:55   ` Alexis Bruemmer
2008-06-04  0:23     ` FUJITA Tomonori
2008-06-12  1:25 ` Alexis Bruemmer
2008-06-12  7:29   ` FUJITA Tomonori
2008-06-12 16:58     ` Alexis Bruemmer

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=20080603052146.GI7011@il.ibm.com \
    --to=muli@il.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexisb@us.ibm.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.