From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrew Morton <akpm@osdl.org>
Cc: ak@suse.de, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Improve pci_alloc_consistent wrapper on preemptive kernels
Date: 30 Jul 2004 16:28:26 -0400 [thread overview]
Message-ID: <1091219306.1727.49.camel@mulgrave> (raw)
In-Reply-To: <20040730132016.5906caa7.akpm@osdl.org>
On Fri, 2004-07-30 at 16:20, Andrew Morton wrote:
> Sounds sane. But the default version in asm-generic/dma-mapping.h needs to
> be fixed up:
>
> static inline void *
> dma_alloc_coherent(struct device *dev, size_t size, dma_addr_t *dma_handle,
> int flag)
> {
> BUG_ON(dev->bus != &pci_bus_type);
>
> return pci_alloc_consistent(to_pci_dev(dev), size, dma_handle);
> }
>
> If we stick with this model, we'll still need a new pci_alloc_consistent_gfp().
Theoretically, that was just to help architectures that didn't want to
implement the dma_ functions. If we make dma_alloc_coherent() the
preferred implementation, we just remove this because now all arch's
will have to implement dma_alloc_coherent anyway.
James
next prev parent reply other threads:[~2004-07-30 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 17:02 [PATCH] Improve pci_alloc_consistent wrapper on preemptive kernels Andi Kleen
2004-07-30 17:16 ` Jeff Garzik
2004-07-30 17:43 ` Andi Kleen
2004-07-30 18:07 ` Jeff Garzik
2004-07-30 18:47 ` Takashi Iwai
2004-07-30 19:28 ` Takashi Iwai
2004-07-30 21:42 ` Andi Kleen
2004-07-30 20:02 ` Andrew Morton
2004-07-30 20:13 ` James Bottomley
2004-07-30 20:20 ` Andrew Morton
2004-07-30 20:28 ` James Bottomley [this message]
[not found] <2nJ3t-34a-39@gated-at.bofh.it>
[not found] ` <2nJmP-3eq-9@gated-at.bofh.it>
[not found] ` <2nJG8-3p6-21@gated-at.bofh.it>
[not found] ` <2nK9b-3PM-17@gated-at.bofh.it>
2004-07-30 18:34 ` Andi Kleen
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=1091219306.1727.49.camel@mulgrave \
--to=james.bottomley@hansenpartnership.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@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