All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Proposal for new generic device API: dma_get_required_mask()
Date: 19 Jun 2004 10:00:50 -0500	[thread overview]
Message-ID: <1087657251.2162.49.camel@mulgrave> (raw)
In-Reply-To: <m3fz8s79dz.fsf@defiant.pm.waw.pl>

On Fri, 2004-06-18 at 18:07, Krzysztof Halasa wrote:
> James Bottomley <James.Bottomley@steeleye.com> writes:
> I don't think so. We already have separate masks for coherent
> and non-coherent mappings (in PCI API, and I'm told it's to be extended
> to DMA API as well). And we need them.
> 
> The problem is we're missing DMA masks for non-alloc calls (depending
> on the platform) and thus that it isn't very reliable. Drivers which
> need this are forced to bounce buffers themselves, and many of them
> will not work on 64-bit platforms (as of ~ 2.6.0, I don't check that
> regularly). And yes, we really need reliable masks for non-alloc
> mappings.

Could you elaborate on this?  In the current scheme the coherent mask is
for descriptor allocation (i.e. dma_alloc_coherent()) and the dma_mask
represents the bus physical addresses to which the device can DMA
directly; there's not much more the DMA API really does, what do you
think is missing?

James

  reply	other threads:[~2004-06-19 15:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 14:08 Proposal for new generic device API: dma_get_required_mask() James Bottomley
2004-06-17 14:51 ` Meelis Roos
2004-06-17 15:28 ` Matthew Wilcox
2004-06-17 20:12   ` James Bottomley
2004-06-18  0:46 ` Krzysztof Halasa
2004-06-18  1:45   ` James Bottomley
2004-06-18 23:07     ` Krzysztof Halasa
2004-06-19 15:00       ` James Bottomley [this message]
2004-06-19 23:39         ` Krzysztof Halasa
2004-06-20 16:56           ` James Bottomley
2004-06-18  9:21   ` Russell King
2004-06-18 23:10     ` Krzysztof Halasa
2004-06-19 20:22       ` Russell King
2004-06-20  0:00         ` Krzysztof Halasa
2004-06-20 19:47           ` Russell King
2004-06-23 19:32             ` Krzysztof Halasa
2004-06-18  5:59 ` Jeremy Higdon
2004-06-18 14:19   ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2004-06-17 14:08 James Bottomley
2004-06-17 14:52 Salyzyn, Mark

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=1087657251.2162.49.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 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.