From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
Linux Kernel list <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>, Greg KH <greg@kroah.com>
Subject: Re: DMA APIs gumble grumble
Date: Wed, 8 Nov 2006 10:25:36 +0200 [thread overview]
Message-ID: <20061108082536.GA3405@rhun.haifa.ibm.com> (raw)
In-Reply-To: <1162950877.28571.623.camel@localhost.localdomain>
On Wed, Nov 08, 2006 at 12:54:37PM +1100, Benjamin Herrenschmidt wrote:
> - For platforms like powerpc where I can have multiple busses on
> different IOMMU's and with possibly different DMA ops, I really need to
> have a per-device data structure for use by the DMA ops (in fact, in my
> case, containing the DMA ops themselves). Right now, I defined a notion
> of "device extension" (struct device_ext) that my current implementation
> puts in device->firmware_data (don't look for it upstream, it's all
> patches queuing up for 2.6.20 and about to go into powerpc.git), but
> that I'd like to have flat in struct device instead. Would it be agreed
> that linux/device.h includes itself an asm/device.h which contains a
> definition for a struct device_ext that is within struct device ? That
> would also avoid a pointer indirection which is a good thing for DMA
> operations
I want multiple dma_ops for Calgary on x86-64, so strong thumbs up for
doing this in a generic manner. device_ext kinda sucks as a name,
though... if it's used for just dma_ops, how about device_dma_ops?
I agree with the rest of your suggestions too, FWIW.
Cheers,
Muli
next prev parent reply other threads:[~2006-11-08 8:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 1:54 DMA APIs gumble grumble Benjamin Herrenschmidt
2006-11-08 4:46 ` David Miller
2006-11-08 5:23 ` Benjamin Herrenschmidt
2006-11-08 5:29 ` David Miller
2006-11-08 5:44 ` Benjamin Herrenschmidt
2006-11-10 1:02 ` Benjamin Herrenschmidt
2006-11-10 2:50 ` David Miller
2006-11-10 2:55 ` Benjamin Herrenschmidt
2006-11-10 3:01 ` David Miller
2006-11-10 4:07 ` Benjamin Herrenschmidt
2006-11-08 8:25 ` Muli Ben-Yehuda [this message]
2006-11-08 8:47 ` Benjamin Herrenschmidt
2006-11-08 9:21 ` Muli Ben-Yehuda
2006-11-08 10:00 ` Benjamin Herrenschmidt
2006-11-08 22:56 ` Russell King
2006-11-08 23:41 ` Benjamin Herrenschmidt
2006-11-09 0:43 ` Benjamin Herrenschmidt
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=20061108082536.GA3405@rhun.haifa.ibm.com \
--to=muli@il.ibm.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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