From: William Chow <lilbilchow@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: is pci_alloc_consistent() really consistent on a pentium?
Date: Thu, 30 May 2002 13:44:06 -0700 (PDT) [thread overview]
Message-ID: <20020530204406.55023.qmail@web13808.mail.yahoo.com> (raw)
If IA32 builds use the i386 version of
pci_alloc_consistent(), how is the memory provided by
this function really write-thru (on a pentium) since
it appears to only set up the default mapping
(PCD/PWT==0)? In contrast, pgprot_noncached() and
pci_mmap_page_range() explicitly set these bits on a
pentium (i.e. when boot_cpu_data.x86 > 3). Or am I
missing something?
Please CC me on the response.
- William Chow
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
next reply other threads:[~2002-05-30 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 20:44 William Chow [this message]
2002-05-30 20:35 ` is pci_alloc_consistent() really consistent on a pentium? David S. Miller
2002-05-31 20:58 ` William Chow
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=20020530204406.55023.qmail@web13808.mail.yahoo.com \
--to=lilbilchow@yahoo.com \
--cc=linux-kernel@vger.kernel.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