LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Russell King <rmk@arm.linux.org.uk>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: DMA mapping API for non-system memory pools
Date: Fri, 9 Feb 2007 17:33:01 -0600	[thread overview]
Message-ID: <4479FB80-8703-4BCA-925E-DA25B65EE916@kernel.crashing.org> (raw)

We've been having a discussion on the linuxppc-dev list about how to  
handle IO memory that exists on some PPC SoC devices.  These IO  
memories behave like system memory but are faster to the processor or  
device needed accessing for things like buffer descriptors.

Here's an example in which allocation is done either via system  
memory or a specialized allocator for MURAM from drivers/net/ucc_geth.c:

(Yes, the system memory should be moved to use the dma mapping api)

                 if (uf_info->bd_mem_part == MEM_PART_SYSTEM) {
                         u32 align = 4;
                         if (UCC_GETH_TX_BD_RING_ALIGNMENT > 4)
                                 align = UCC_GETH_TX_BD_RING_ALIGNMENT;
                         ugeth->tx_bd_ring_offset[j] =
                                 kmalloc((u32) (length + align),  
GFP_KERNEL);

                         if (ugeth->tx_bd_ring_offset[j] != 0)
                                 ugeth->p_tx_bd_ring[j] =
                                         (void*)((ugeth- 
 >tx_bd_ring_offset[j] +
                                         align) & ~(align - 1));
                 } else if (uf_info->bd_mem_part == MEM_PART_MURAM) {
                         ugeth->tx_bd_ring_offset[j] =
                             qe_muram_alloc(length,
                                             
UCC_GETH_TX_BD_RING_ALIGNMENT);
                         if (!IS_MURAM_ERR(ugeth->tx_bd_ring_offset[j]))
                                 ugeth->p_tx_bd_ring[j] =
                                     (u8 *) qe_muram_addr(ugeth->
                                                           
tx_bd_ring_offset[j]);
                 }

ideally all this would be handled via the dma mapping API, the  
question is how to convey to the API to use the IO memory vs the  
system memory?  Should we look at adding a new GFP_IOMEM flag or do  
something based on struct device?

Any ideas on direction (or if this is a solved problem elsewhere)  
would be appreciated.

Thanks

- kumar

             reply	other threads:[~2007-02-09 23:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 23:33 Kumar Gala [this message]
2007-02-09 23:53 ` James Bottomley
2007-02-09 23:54 ` Matthew Jacob

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=4479FB80-8703-4BCA-925E-DA25B65EE916@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --subject='Re: DMA mapping API for non-system memory pools' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).