From: Arjan van de Ven <arjan@infradead.org>
To: Marcelo Tosatti <marcelo@kvack.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, olpc-devel@laptop.org
Subject: Re: [PATCH] introduce config option to disable DMA zone on i386
Date: Thu, 28 Dec 2006 18:43:03 +0100 [thread overview]
Message-ID: <1167327784.3281.4341.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20061228170302.GA4335@dmt>
On Thu, 2006-12-28 at 15:03 -0200, Marcelo Tosatti wrote:
> Hi,
>
> The following patch adds a config option to get rid of the DMA zone on i386.
>
> Architectures with devices that have no addressing limitations (eg. PPC)
> already work this way.
>
> This is useful for custom kernel builds where the developer is certain that
> there are no address limitations.
>
> For example, the OLPC machine contains:
>
> - USB devices
> - no floppy
> - no address limited PCI devices
> - no floppy
>
> A unified zone simplifies VM reclaiming work, and also simplifies OOM
> killer heuristics (no need to deal with OOM on the DMA zone).
>
> Comments?
Hi,
since one gets random corruption if a user gets this wrong, at least
make things like floppy and all CONFIG_ISA stuff conflict with this
option.... without that your patch feels like a walking time bomb...
(and please include all PCI drivers that only can do 24 bit or 28bit
or .. non-32bit dma as well)
Greetings,
Arjan van de Ven
--
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>
next prev parent reply other threads:[~2006-12-28 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 17:03 Marcelo Tosatti
2006-12-28 17:30 ` Paul Mundt
2006-12-28 17:43 ` Arjan van de Ven [this message]
2006-12-28 18:36 ` Jan Engelhardt
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=1167327784.3281.4341.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@kvack.org \
--cc=olpc-devel@laptop.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