public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Andi Kleen <ak@suse.de>, "H. Peter Anvin" <hpa@zytor.com>,
	Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: GFP_DMA32 and PAE x86 machines
Date: Wed, 30 May 2007 16:21:01 -0700	[thread overview]
Message-ID: <20070530232101.GG6909@holomorphy.com> (raw)
In-Reply-To: <21d7e9970705301609w88a9f80t20f83806003f699e@mail.gmail.com>

On 5/31/07, Andi Kleen <ak@suse.de> wrote:
>> Please give a very very strong rationale why you want it. Did you actually
>> run into such a situation yourself yet?

On Thu, May 31, 2007 at 09:09:58AM +1000, Dave Airlie wrote:
> Funnily enough I have just today with an app I have which uses 1.2GB
> of textures :-)
> we are currently using GFP_DMA32 in the TTM allocator code, however
> what I really want on x86 non-PAE is GFP_HIGHMEM (as DMA32 does
> nothing) however on x86-PAE I don't want that I want a real GFP_DMA32,
> and on x86-64 I want the current GFP_DMA32,
> Therein lies my problems, the API sucks, but I suppose the DRM TTM is
> a special use case (AGP is the same) and I'll accept the fact that can
> just make it my own problem, my current solution would be to screw PAE
> machines giving them 1GB only and let non-PAE access all 4GB.

It's easy enough to spin kernels that allow 4GB-constrained highmem
allocations. The real question is whether it'll be merged.


-- wli

  reply	other threads:[~2007-05-30 23:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 21:10 GFP_DMA32 and PAE x86 machines Dave Airlie
2007-05-30 21:29 ` H. Peter Anvin
2007-05-30 22:07   ` Dave Airlie
2007-05-30 22:13     ` H. Peter Anvin
2007-05-30 22:24     ` Andi Kleen
2007-05-30 22:31       ` H. Peter Anvin
2007-05-30 23:09       ` Dave Airlie
2007-05-30 23:21         ` William Lee Irwin III [this message]
2007-05-31 12:11         ` Andi Kleen

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=20070530232101.GG6909@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=airlied@gmail.com \
    --cc=ak@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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