mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ioe-lkml@rameria.de>
To: fc scsi <scsi_fc_group@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: _PAGE_PCD bit in DMAable memory
Date: Tue, 18 May 2004 22:29:20 +0200	[thread overview]
Message-ID: <200405182229.23737.ioe-lkml@rameria.de> (raw)
In-Reply-To: <20040518190319.95305.qmail@web50004.mail.yahoo.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 18 May 2004 21:03, you wrote:
> Thanks much for the reply. I forgot to mention I am on
> Linux 2.4.20. I looked into 2.6 and could see what you
> described in your email. The comment on top of
> consistent_alloc() for arm (2.4.20) says it will give
> cache-coherent memory, but i am not able to see how
> this is made possible for Xscale when if it doesn't
> set the L_PTE_CACHEABLE to 0 (for 2.4.20, again).

There it is hidden in arch/arm/mm/ioremap.c

look at the L_ flags there and how L_PTE_CACHEABLE is missing there by default.

PS: This can be found easily with grep. Try this little Bash script to grep recursively 
      through the kernel and answer your questions more quickly:

#!/bin/bash
if [ $# -lt 2 ]; then
        PROGNAME=`basename $0`
        echo -e "$PROGNAME - find a string in a tree of *.c and *.h files"
        echo -e "Usage:\t$PROGNAME <start dir> <what>\n"
        exit 1
fi

DIR=$1
shift
exec find "${DIR}" -type f -name '*.[ch]' -print0 |xargs -0 grep -A8 "$@"


Regards

Ingo Oeser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAqnIhU56oYWuOrkARAv6xAKCgcq/WebDhbLunZA9m/MnDhbKAVgCffZDE
SPn4VpSWK57wFxjmdicyIok=
=KjNv
-----END PGP SIGNATURE-----

       reply	other threads:[~2004-05-18 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040518190319.95305.qmail@web50004.mail.yahoo.com>
2004-05-18 20:29 ` Ingo Oeser [this message]
2004-05-17  1:12 fc scsi
2004-05-17  2:20 ` Roland Dreier
2004-05-17 15:48   ` fc scsi

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=200405182229.23737.ioe-lkml@rameria.de \
    --to=ioe-lkml@rameria.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scsi_fc_group@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®