From: "Adam J. Richter" <adam@yggdrasil.com>
To: benh@kernel.crashing.org
Cc: James.Bottomley@steeleye.com, linux-kernel@vger.kernel.org,
miles@gnu.org
Subject: Re: [RFC] generic device DMA implementation
Date: Thu, 5 Dec 2002 04:13:29 -0800 [thread overview]
Message-ID: <200212051213.EAA04698@adam.yggdrasil.com> (raw)
Benjamin Herrenschmidt wrote:
>On Wed, 2002-12-04 at 22:46, James Bottomley wrote:
>> If you have a machine that has both consistent and inconsistent blocks, you
>> need to encode that in dma_addr_t (which is a platform definable type).
>
>I don't agree here. Encoding things in dma_addr_t, then special casing
>in consistent_{map,unmap,sync,....) looks really ugly to me ! You want
>dma_addr_t to contain a bus address for the given bus you are working
>with and pass that to your device, period.
I don't think that James meant actually defining flag bits
inside of dma_addr_t, although I suppose you could do it for some
unused high bits on some architectures. I think the implication
was that you could have something like:
static inline int is_consistent(dma_addr_t addr)
{
return (addr >= CONSISTENT_AREA_START && addr < CONSISTENT_AREA_END);
}
I also don't recall anyone proposing special casing
dma_{map,unmap,sync} based on the results of such a check. I think
the only function that might use it would be maybe_wmb(addr,len),
which, on some might machines might be:
static inline void maybe_wmb(dma_addr_t addr, size_t len)
{
if (!is_consistent(addr))
wmb();
}
In practice, I think dma_malloc() would either always return
consistent memory or never return consistent memory on a given
machine, so maybe_wmb would probably never do such range checking.
Instead it would compile to nothing on machines where dma_alloc always
returned consistent memory, would compile to wmb() on systems where
dma_alloc would only succeed if it could return non-consistent memory,
and would compile to a procedure pointer on parisc that would either
set to point to a no-op or wmb, depending on which kind of machine the
kernel was booted on.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
next reply other threads:[~2002-12-05 12:08 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 12:13 Adam J. Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-07 14:37 Adam J. Richter
2002-12-07 4:12 Adam J. Richter
2002-12-06 22:52 Adam J. Richter
2002-12-06 22:17 Adam J. Richter
2002-12-06 22:26 ` James Bottomley
2002-12-06 22:29 ` David S. Miller
2002-12-06 22:48 ` James Bottomley
2002-12-06 22:49 ` David S. Miller
2002-12-06 22:32 ` Arjan van de Ven
2002-12-06 17:39 Adam J. Richter
2002-12-06 18:07 ` Matthew Wilcox
2002-12-06 17:07 Adam J. Richter
2002-12-06 16:48 James Bottomley
2002-12-06 16:19 Adam J. Richter
2002-12-06 16:40 ` Matthew Wilcox
2002-12-06 18:17 ` David S. Miller
2002-12-06 18:29 ` James Bottomley
2002-12-06 18:31 ` David S. Miller
2002-12-06 18:40 ` James Bottomley
2002-12-06 18:42 ` David S. Miller
2002-12-06 21:04 ` Oliver Xymoron
2002-12-07 10:19 ` David Gibson
2002-12-06 18:36 ` Matthew Wilcox
2002-12-06 18:38 ` David S. Miller
2002-12-06 7:41 Adam J. Richter
2002-12-06 15:50 ` David S. Miller
2002-12-06 7:14 Adam J. Richter
2002-12-06 16:26 ` James Bottomley
2002-12-06 17:48 ` Miles Bader
2002-12-07 9:56 ` David Gibson
2002-12-07 9:45 ` David Gibson
2002-12-07 11:26 ` Russell King
2002-12-08 5:28 ` David Gibson
2002-12-06 6:15 David Brownell
2002-12-06 2:08 Adam J. Richter
2002-12-06 2:53 ` David Gibson
2002-12-06 4:03 ` David S. Miller
2002-12-05 20:27 Adam J. Richter
2002-12-05 17:49 Manfred Spraul
2002-12-06 0:08 ` David Gibson
2002-12-05 12:21 Adam J. Richter
2002-12-05 12:44 ` Russell King
2002-12-05 11:57 Adam J. Richter
2002-12-06 0:06 ` David Gibson
2002-12-05 5:20 Adam J. Richter
2002-12-05 3:02 Adam J. Richter
2002-12-05 6:15 ` David Gibson
2002-12-05 1:21 Adam J. Richter
2002-12-05 2:40 ` David Gibson
2002-12-05 2:49 ` Miles Bader
2002-12-05 6:12 ` David Gibson
2002-12-05 0:43 Adam J. Richter
2002-12-05 0:55 ` Jeff Garzik
2002-12-05 2:02 ` James Bottomley
2002-12-04 17:47 James Bottomley
2002-12-04 18:27 ` Jeff Garzik
2002-12-04 19:36 ` James Bottomley
2002-12-04 21:19 ` Miles Bader
2002-12-04 21:21 ` Miles Bader
2002-12-04 21:42 ` James Bottomley
2002-12-05 5:44 ` Miles Bader
2002-12-04 21:46 ` James Bottomley
2002-12-05 2:31 ` Miles Bader
2002-12-05 3:06 ` James Bottomley
2002-12-05 5:02 ` David Gibson
2002-12-05 11:15 ` Benjamin Herrenschmidt
2002-12-05 11:16 ` William Lee Irwin III
2002-12-05 15:12 ` James Bottomley
2002-12-05 0:47 ` David Gibson
2002-12-05 0:54 ` Jeff Garzik
2002-12-05 1:44 ` James Bottomley
2002-12-05 2:38 ` David Gibson
2002-12-05 3:13 ` James Bottomley
2002-12-05 5:05 ` David Gibson
2002-12-05 15:03 ` James Bottomley
2002-12-05 23:54 ` David Gibson
2002-12-05 3:17 ` Miles Bader
2002-12-05 6:06 ` David Gibson
2002-12-05 6:43 ` Miles Bader
2002-12-05 23:44 ` David Gibson
2002-12-06 2:23 ` Miles Bader
2002-12-05 3:41 ` Jeff Garzik
2002-12-05 6:04 ` David Gibson
2002-12-05 16:29 ` Jeff Garzik
2002-12-05 23:59 ` David Gibson
2002-12-05 11:08 ` Benjamin Herrenschmidt
2002-12-05 11:35 ` Russell King
2002-12-05 15:24 ` James Bottomley
2002-12-06 0:01 ` David Gibson
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=200212051213.EAA04698@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=James.Bottomley@steeleye.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.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
Powered by JetHome