All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linux-arch@vger.kernel.org
Subject: Re: Accessing memory remote across the bus in the same way as local memory
Date: 19 Jun 2004 09:02:56 -0500	[thread overview]
Message-ID: <1087653778.2121.29.camel@mulgrave> (raw)
In-Reply-To: <16595.48028.925656.212915@cargo.ozlabs.ibm.com>

On Fri, 2004-06-18 at 23:05, Paul Mackerras wrote:
> Not on iSeries machines (ppc64 machines running OS/400).  There we
> have to do a hypervisor call for every access to PCI memory or I/O
> space, unfortunately.  Fortunately people don't tend to put arbitrary
> PCI adaptors in iSeries boxes, and they don't run X servers.  Linux
> partitions on iSeries machines are mostly used for things like
> firewalls and web servers.

Heh, I guessed there'd be one architecture that couldn't do this.

> What did you want to be able to do this for?  It probably isn't the
> end of the world if whatever you want to do with this doesn't work on
> iSeries.

The basic issue is can we declare memory that resides on a device chip
(or on a memory controller behind a PCI bridge) to the system so that it
can be used almost identically to real memory (just with a bunch of
restrictions).

The request is coming from an ARM developer who has an OHCI chip with 32
on chip sram.  He wants dma_alloc_coherent() to hand out the on-chip
memory so that he doesn't have to modify the generic OHCI driver to be
able to use a separate memory area.

However, most modern devices seem to come with on-board memory for
descriptors, ring buffers and the like (mainly for efficiency since the
device can access them without having to do a bus to main memory
transaction), so I was wondering if allocating from this on-board pool
could be folded into the DMA API so that dma_alloc_coherent() could
manage it for every such device.

James

      reply	other threads:[~2004-06-19 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 23:26 Accessing memory remote across the bus in the same way as local memory James Bottomley
2004-06-18 23:32 ` David S. Miller
2004-06-18 23:43   ` James Bottomley
2004-06-19  4:05 ` Paul Mackerras
2004-06-19 14:02   ` James Bottomley [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=1087653778.2121.29.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-arch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.