linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Greg Johnson <gjohnson@research.canon.com.au>
Cc: Linux PPC Mailing List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: User buffers and cache flushing.
Date: Thu, 09 Mar 2000 21:49:10 -0500	[thread overview]
Message-ID: <38C862A6.224DBDF3@embeddededge.com> (raw)
In-Reply-To: 20000310010235.6B0D3355C8@elph.research.canon.com.au


Greg Johnson wrote:

> ....Since I
> am not wanting to be double handling this data, and the data will
> most likely be fragmented in memory,

That's no problem, CPM buffer descriptors are made for that.


> ....and call flush_dcache_range on each of these fragments.

Depends upon how the data is handled.  In some cases I find it is
faster to just map the pages uncached and skip the cache push.  Do
some system design and analysis to determine what works best.

> Have I overlooked anything? (other than the lack of support for IDMA
> currently in the MPC8xx kernel)

This is pretty trivial, considering all CPM devices use the same DMA
engine as IDMA.  Take an existing driver, rip the guts of data comm
out of it, and you nearly have the IDMA driver.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-03-10  2:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-10  1:02 User buffers and cache flushing Greg Johnson
2000-03-10  2:49 ` Dan Malek [this message]
2000-03-16  2:40   ` Greg Johnson
2000-03-16 10:07     ` Marcus Sundberg
2000-03-16 14:08       ` Brad Parker
2000-03-16 21:48       ` Greg Johnson

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=38C862A6.224DBDF3@embeddededge.com \
    --to=dan@netx4.com \
    --cc=gjohnson@research.canon.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).