public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 5/6] Optional ZONE_DMA for x86_64
Date: Tue, 12 Sep 2006 06:40:22 +0000	[thread overview]
Message-ID: <200609120840.22808.ak@suse.de> (raw)
In-Reply-To: <20060911222755.4849.17749.sendpatchset@schroedinger.engr.sgi.com>

On Tuesday 12 September 2006 00:27, Christoph Lameter wrote:
> x86_64: optional ZONE_DMA/ZONE_DMA32
>
> Allow the use to specify CONFIG_ZONE_DMA32 and CONFIG_ZONE_DMA (via
> CONFIG_GENERIC_ISA_DMA).
>
> If CONFIG_ZONE_DMA is off then devices requiring ISA DMA can no
> longer be selected.
>
> There are no drivers depending on CONFIG_ZONE_DMA32. If CONFIG_ZONE_DMA32
> is not set then the system assumes that DMA devices are capable of
> doing DMA to all of memory (which is mostly the case since most
> x86_64 motherboards only allow a max of 4GB of memory and advanced
> systems have DMA subsystems that handle I/O properly).

Pretty much all have this problem (or do you know of a system with no
USB controller?) 

I think I would prefer to not make GFP_DMA32 optional.
Adding a 4GB limit CONFIG to a 64bit kernel just seems somewhat
dumb.

Also what happens when someone still sets GFP_DMA? 
iirc the SCSI stack tended to do that for some structures.
Will it fail?

Making GFP_DMA optional would be an interesting
experiment (I think it will break the floppies but other than that 
a modern system might be fine). But it would be better
to warn the user stronger against it (most likely it will still
break a lot of older addin cards) and tell them about
the floppy.

BTW we still call it x86-64, not x64.

-Andi

  reply	other threads:[~2006-09-12  6:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-11 22:27 [PATCH 5/6] Optional ZONE_DMA for x86_64 Christoph Lameter
2006-09-12  6:40 ` Andi Kleen [this message]
2006-09-12 11:11 ` Andi Kleen
2006-09-12 11:40 ` Matthew Wilcox
2006-09-12 17:28 ` Christoph Lameter

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=200609120840.22808.ak@suse.de \
    --to=ak@suse.de \
    --cc=linux-ia64@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