linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul White <pwhite@networkrobots.com>
To: Dan Malek <dan@mvista.com>, jtm@smoothsmoothie.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: (allocating non-cachable memory) (or More on the i82596)
Date: Fri, 29 Jun 2001 10:48:45 -0700	[thread overview]
Message-ID: <200106291744.f5THia810339@stimpy.networkrobots.com> (raw)
In-Reply-To: <3B3C30CD.34B20F02@mvista.com>


Btw...Where are these "consistent_alloc()" functions?  I've not seen theses
anywhere.

I also can't imagine how they would possibly work on any CPU using BATs.
Since the BAT is setup as cacheable space, you can't just take a "chunk"
of it and make it non-cacheable.  Not possible.

Now, yes, for the 4xx and 8xx proccessors that don't use BATs, I would
assume that when you do one of these "non-cache" allocs, it would
simply allocate you a batch of 4k pages, and set them as Caching
Inhibited.

Is there something I'm missing here?

Paul W.

At 03:39 AM 6/29/2001 -0400, Dan Malek wrote:
>
>jtm@smoothsmoothie.com wrote:
>
>> .... The buffer memory will get filled
>> via DMA, and therefore must not be cached.
>
>Huh????  The 8260 is cache coherent, you don't need to do that.
>
>For processors that are not cache coherent (4xx and 8xx), there
>are standard 'consistent_alloc()' functions available.
>
>
>	-- Dan
>
>
-------------------------------------------------------------
Network Robots, Inc.         /--\               Paul H. White
                           / ____ \
4695 Chabot Dr. #200      / ( oo ) \       Software Developer
Pleasanton, CA 94588     /   ----   \             Engineering
(925) 924-8600           \   ----   /          (925) 580-4883
                          \  V--V  /
                           \      /
                             \--/

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

  parent reply	other threads:[~2001-06-29 17:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 10:22 (allocating non-cachable memory) (or More on the i82596) Justin (Gus) Hurwitz
2001-06-26 21:08 ` jtm
2001-06-28  8:52   ` Justin (Gus) Hurwitz
2001-06-29  7:39   ` Dan Malek
2001-06-29  5:21     ` Justin (Gus) Hurwitz
2001-06-29  6:58     ` Justin (Gus) Hurwitz
2001-07-01  5:04       ` Dan Malek
2001-06-29 16:30     ` jtm
2001-06-29 17:55       ` Paul White
2001-06-29 17:45     ` Paul White
2001-06-29 17:48     ` Paul White [this message]
2001-06-29 15:41       ` Matt Porter
2001-07-01  5:07         ` Dan Malek
2001-07-05 10:11         ` Justin (Gus) Hurwitz
2001-07-05 20:00           ` Dan Malek
2001-07-01  5:09       ` Dan Malek
2001-07-01  6:45         ` Paul White
     [not found] <200106281622.f5SGMW810376@stimpy.networkrobots.com>
2001-06-28 10:43 ` Justin (Gus) Hurwitz
     [not found] ` <Pine.LNX.3.95.1010628062229.5112E-100000@november.bhjjh.er ols.com>
2001-06-29  0:13   ` Paul White
2001-06-29  9:16     ` Justin (Gus) Hurwitz
     [not found]     ` <Pine.LNX.3.95.1010629042746.5292E-100000@november.bhjjh.er ols.com>
2001-06-29 17:53       ` Paul White
2001-06-29 12:11         ` Justin (Gus) Hurwitz
2001-07-01  5:17           ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2001-06-28 16:28 Paul White

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=200106291744.f5THia810339@stimpy.networkrobots.com \
    --to=pwhite@networkrobots.com \
    --cc=dan@mvista.com \
    --cc=jtm@smoothsmoothie.com \
    --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).