linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
	airlied@redhat.com, dri-devel@lists.sf.net,
	linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org,
	eric@anholt.net, stable@kernel.org, linux-mm@kvack.org,
	shaohua.li@intel.com
Subject: Re: [PATCH] drm: i915: ensure objects are allocated below 4GB on PAE
Date: Tue, 26 May 2009 20:18:40 -0400	[thread overview]
Message-ID: <20090527001840.GC16929@bombadil.infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0905262343140.13452@sister.anvils>

On Tue, May 26, 2009 at 11:55:50PM +0100, Hugh Dickins wrote:
> I'm confused: I thought GFP_DMA32 only applies on x86_64:
> my 32-bit PAE machine with (slightly!) > 4GB shows no ZONE_DMA32.
> Does this patch perhaps depend on another, to enable DMA32 on 32-bit
> PAE, or am I just in a muddle?
> 

No, you're exactly right, I'm just a muppet and missed the obvious.
Looks like the "correct" fix is the fact that the allocation is thus
filled out with GFP_USER, therefore, from ZONE_NORMAL, and below
max_low_pfn.

Looks like we'll need some additional thinking to get true ZONE_DMA32 on
i386... ugh, I'll look into it tonight.

regards, Kyle

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-05-27  0:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 16:27 Kyle McMartin
2009-05-26 19:17 ` Peter Zijlstra
2009-05-26 21:35   ` Eric Anholt
2009-05-26 21:41     ` Peter Zijlstra
2009-05-26 21:43       ` Kyle McMartin
2009-05-26 22:55 ` Hugh Dickins
2009-05-27  0:18   ` Kyle McMartin [this message]
2009-05-27  0:42     ` Shaohua Li
2009-05-27 17:40       ` Eric Anholt
2009-05-27 18:23         ` Kyle McMartin
2009-05-31  0:49         ` Shaohua Li

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=20090527001840.GC16929@bombadil.infradead.org \
    --to=kyle@mcmartin.ca \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.sf.net \
    --cc=eric@anholt.net \
    --cc=hugh.dickins@tiscali.co.uk \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shaohua.li@intel.com \
    --cc=stable@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