All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: [PATCH: x86] Add dma_mmap_coherent()
Date: Sun, 28 Mar 2004 13:36:33 +0100	[thread overview]
Message-ID: <20040328133633.F2825@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040328114047.GO791@holomorphy.com>; from wli@holomorphy.com on Sun, Mar 28, 2004 at 03:40:47AM -0800

On Sun, Mar 28, 2004 at 03:40:47AM -0800, William Lee Irwin III wrote:
> I think we're just missing an API for it e.g. break_compound_page();
> I don't see why we shouldn't arrange for it. Alternatively, clearing
> PG_compound by hand is possible. Though I guess it raises the question
> of what we're trying to do; e.g. why not allocate pieces separately?

dma_alloc_coherent() is supposed to allocate a contiguous memory area.

However, x86 can get around this problem if it uses the ->nopage
method of mapping the pages into memory.

This all brings up one fundamental question: what really are the
semantics of dma_alloc_coherent() - if it returns a kernel direct
mapped address, are the pages supposed to be marked reserved or not.

And this leads on to this question: if the pages are not marked
reserved, how do we mmap() the pages given that remap_page_range()
won't touch them?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-03-28 12:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-28 10:22 [PATCH: x86] Add dma_mmap_coherent() Russell King
2004-03-28 10:40 ` [PATCH: ARM] " Russell King
2004-03-28 11:35 ` [PATCH: x86] " Russell King
2004-03-28 11:40   ` William Lee Irwin III
2004-03-28 12:36     ` Russell King [this message]
2004-03-28 12:51       ` William Lee Irwin III
2004-03-28 13:19       ` Russell King

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=20040328133633.F2825@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-arch@vger.kernel.org \
    --cc=wli@holomorphy.com \
    /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.