public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Linux Arch list <linux-arch@vger.kernel.org>
Subject: Re: More DMA API junk
Date: Tue, 16 Mar 2004 12:17:47 +0100	[thread overview]
Message-ID: <20040316111747.GA1592@linux-mips.org> (raw)
In-Reply-To: <1079408930.2158.408.camel@mulgrave>

On Mon, Mar 15, 2004 at 10:48:48PM -0500, James Bottomley wrote:

> You're confused about what it's used for.  It's designed only to be
> called on memory allocated by dma_alloc_noncoherent() and tells you if
> that API actually returned coherent memory or not.  This was designed

... but what is coherent?  The API's function naming is completly confusing
at least from a MIPS perspective.  MIPS calls something coherent if
cache coherency is maintained by hardware and that's (hey, what caches?!?)
not the case for uncached memory.

So I would like to rename functions to something less confusing.  Where
did the original terminology come from?  Would anybody object simply
swapping the coherent and noncoherent parts of the function names?

  Ralf

      parent reply	other threads:[~2004-03-16 11:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16  0:53 More DMA API junk Benjamin Herrenschmidt
2004-03-16  1:12 ` James Bottomley
2004-03-16  1:32   ` Benjamin Herrenschmidt
2004-03-16  3:24     ` James Bottomley
2004-03-16  3:32       ` Benjamin Herrenschmidt
2004-03-16  3:48         ` James Bottomley
2004-03-16  3:53           ` Benjamin Herrenschmidt
2004-03-16 11:17           ` Ralf Baechle [this message]

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=20040316111747.GA1592@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-arch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox