public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <ak@suse.de>
Cc: Dave Airlie <airlied@gmail.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 15:31:01 -0700	[thread overview]
Message-ID: <465DFB25.4070009@zytor.com> (raw)
In-Reply-To: <200705310024.25937.ak@suse.de>

Andi Kleen wrote:
> On Thursday 31 May 2007 00:07:45 Dave Airlie wrote:
>> Depending on split all lowmem is below 1GB which isn't exactly
>> optimal, I'd llike all 4GB for DMA.
> 
> Well it would be for a quite specialized limited use case: 
> - Memory the kernel doesn't need to map (after all kmap is evil) 
> - You need more than 500MB or so.
> - 32bit kernel and user cannot run 64bit kernel
> - Machine has >3GB of RAM 

There aren't really a whole lot of 32-bit boxen with > 4 GB of RAM (for
4 GB or less -- 2-3 GB or less if the chipset supports remapping --
normal HIGHMEM is all in the required area), and the few that are tend
to be running specialized applications (git.kernel.org is one of those
machines.)

Since it appears that legacy memory standards, SDRAM and DDR-1, aren't
dropping in price like DDR-2 is, I suspect that will more or less remain
that way.

The other problem -- which is a problem in general -- is the
proliferation of DMA masks, and that doesn't look like it's going to get
any better.

	-hpa

  reply	other threads:[~2007-05-30 22:31 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 [this message]
2007-05-30 23:09       ` Dave Airlie
2007-05-30 23:21         ` William Lee Irwin III
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=465DFB25.4070009@zytor.com \
    --to=hpa@zytor.com \
    --cc=airlied@gmail.com \
    --cc=ak@suse.de \
    --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