From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Conke Hu <conke.hu@amd.com>
Cc: Jun Sun <jsun@junsun.net>,
linux-kernel@vger.kernel.org,
Christoph Lameter <clameter@sgi.com>
Subject: RE: Can Linux live without DMA zone?
Date: Thu, 02 Nov 2006 08:13:11 +0100 [thread overview]
Message-ID: <1162451591.27131.2.camel@taijtu> (raw)
In-Reply-To: <FFECF24D2A7F6D418B9511AF6F358602F2D4E1@shacnexch2.atitech.com>
On Thu, 2006-11-02 at 11:43 +0800, Conke Hu wrote:
> It seems a good idea.
> Is dma zone is still necessay on most modern computers?
(don't top post!)
if you would have used google, you'd have found this:
http://www.mail-archive.com/linux-arch@vger.kernel.org/msg01623.html
cheers
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Jun Sun
> Sent: 2006年11月2日 10:16
> To: linux-kernel@vger.kernel.org
> Subject: Can Linux live without DMA zone?
>
>
> I am trying to reserve a block of memory (>16MB) starting from 0 and hide it
> from kernel. A consequence is that DMA zone now has size 0. That causes
> many drivers to grief (OOMs).
>
> I see two ways out:
>
> 1. Modify individual drivers and convince them not to alloc with GFP_DMA.
> I have been trying to do this but do not seem to see an end of it. :)
>
> 2. Simply lie and increase MAX_DMA_ADDRESS to really big (like 1GB) so that
> the whole memory region belongs to DMA zone.
>
> #2 sounds pretty hackish. I am sure something bad will happen
> sooner or later (like what?). But so far it appears to be working fine.
>
> The fundamental question is: Has anybody tried to run Linux without 0 sized
> DMA zone before? Am I doing something that nobody has done before (which is
> something really hard to believe these days with Linux :P)?
>
> Cheers.
>
> Jun
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2006-11-02 7:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 3:43 Can Linux live without DMA zone? Conke Hu
2006-11-02 7:13 ` Peter Zijlstra [this message]
2006-11-02 16:13 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2006-11-02 10:33 Conke Hu
2006-11-02 10:51 ` Arjan van de Ven
2006-11-02 13:09 ` Alan Cox
2006-11-02 2:15 Jun Sun
2006-11-02 9:16 ` Arjan van de Ven
2006-11-02 10:32 ` Paul Mundt
2006-11-02 16:32 ` Phillip Susi
2006-11-02 16:57 ` Arjan van de Ven
2006-11-02 19:08 ` Phillip Susi
2006-11-02 20:10 ` Arjan van de Ven
2006-11-02 21:26 ` Phillip Susi
2006-11-02 22:19 ` Arjan van de Ven
2006-11-02 23:17 ` Jun Sun
2006-11-02 23:24 ` Stephen Hemminger
2006-11-06 2:19 ` Phillip Susi
2006-11-03 17:54 ` Krzysztof Halasa
2006-11-02 18:02 ` Alan Cox
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=1162451591.27131.2.camel@taijtu \
--to=a.p.zijlstra@chello.nl \
--cc=clameter@sgi.com \
--cc=conke.hu@amd.com \
--cc=jsun@junsun.net \
--cc=linux-kernel@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