All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Olaf Hering <olh@suse.de>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: consistent_sync_for_cpu() and friends on ppc32
Date: Tue, 16 Mar 2004 08:59:16 +1100	[thread overview]
Message-ID: <1079387955.1966.177.camel@gaston> (raw)
In-Reply-To: <20040315123647.4ce943b7.davem@redhat.com>


> Ben, can you work this out?  I can make it compile by just making the
> _for_cpu and _for_device routines behave identically to what the
> consisten_sync{,_page}() stuff does now.  But I'd much rather a ppc32
> person implement it correctly and optimally.
> 
> In short, the _for_device routines should make sure cacheable data in
> the cpu is fully visible to the DMA device, and _for_cpu should make
> sure all device DMA is visible to the processor.

Yup, it depends for what CPU the kernel is compiled, normal desktop
CPUs are completely coherent, so this will be a no-op, but 4xx/8xx
embedded CPUs will need something better. I'll have a look today

Ben.



  reply	other threads:[~2004-03-15 22:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15 20:16 consistent_sync_for_cpu() and friends on ppc32 Olaf Hering
2004-03-15 20:36 ` David S. Miller
2004-03-15 21:59   ` Benjamin Herrenschmidt [this message]
2004-03-16  0:23   ` Benjamin Herrenschmidt
2004-03-16  0:49     ` David S. Miller
2004-03-16  1:36       ` Benjamin Herrenschmidt
2004-03-16 18:46         ` David S. Miller
2004-03-16 21:54           ` Benjamin Herrenschmidt

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=1079387955.1966.177.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.de \
    /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.