Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: Matthew Wilcox <willy@debian.org>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] EISA 100/10 add-on card causes kernel BUG
Date: Sun, 17 Mar 2002 13:43:30 +0000	[thread overview]
Message-ID: <20020317134330.F21765@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20020317053838.683C7482D@dsl2.external.hp.com>; from grundler@dsl2.external.hp.com on Sat, Mar 16, 2002 at 10:38:38PM -0700

On Sat, Mar 16, 2002 at 10:38:38PM -0700, Grant Grundler wrote:
> oh - I forgot about those for filling the IO pdir entries...
> that need to change in order to support zero copy?
> 
> We somehow need to pass the spaceID of the userspace buffer
> to dma code if we want DMA to be cache coherent.
> I don't have any good ideas for this.

My understanding is that DMA to userspace is to pages in the page cache
only.  As such, the normal mechanisms for dcache coherency should be used.
That is, DMA to a kernel view of the page and call flush_dcache_page
after touching it.  My proposed scheme for kmap/kunmap implementation
would make flush_dcache_page a no-op, since the kernel would have a view
of the page which is automatically cache coherent with userspace's view.

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2002-03-17 13:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-16  5:50 [parisc-linux] EISA 100/10 add-on card causes kernel BUG Rafael E. Herrera
2002-03-16 18:42 ` Grant Grundler
2002-03-16 21:39   ` Matthew Wilcox
2002-03-17  5:38     ` Grant Grundler
2002-03-17 13:43       ` Matthew Wilcox [this message]
2002-03-17 16:59         ` Grant Grundler
2002-03-22  3:16 ` [parisc-linux] EISA 100/10 add-on card on a 715/80 Rafael E. Herrera

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=20020317134330.F21765@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=grundler@dsl2.external.hp.com \
    --cc=parisc-linux@lists.parisc-linux.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