From: Matt Porter <mporter@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Does kmalloc on MPC82xx work correctly with GFP_DMA?
Date: Tue, 19 Oct 2004 07:31:22 -0700 [thread overview]
Message-ID: <20041019073122.B29957@home.com> (raw)
In-Reply-To: <BE328096-211A-11D9-8079-003065F9B7DC@embeddededge.com>; from dan@embeddededge.com on Mon, Oct 18, 2004 at 11:31:12AM -0400
On Mon, Oct 18, 2004 at 11:31:12AM -0400, Dan Malek wrote:
> No, the kmalloc() space is not covered by BATs (but, that isn't
> relevant for this discussion).
Dan, I think you forgot that green book PPCs get kernel lowmem
("kmalloc() space") covered by BATs if possible...unless you
pass in "nobats".
-Matt
next prev parent reply other threads:[~2004-10-19 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 4:01 SCC UART hang Jeff Angielski
2004-10-18 9:30 ` Does kmalloc on MPC82xx work correctly with GFP_DMA? Conor McLoughlin
2004-10-18 15:31 ` Dan Malek
2004-10-19 8:36 ` Conor McLoughlin
2004-10-19 14:15 ` Dan Malek
2004-10-19 15:26 ` Conor McLoughlin
2004-10-19 14:31 ` Matt Porter [this message]
2004-10-19 14:27 ` Matt Porter
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=20041019073122.B29957@home.com \
--to=mporter@kernel.crashing.org \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.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).