From: Paul Mundt <lethal@linux-sh.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Lameter <clameter@sgi.com>,
linux-mm@vger.kernel.org, Nick Piggin <nickpiggin@yahoo.com.au>,
linux-ia64@vger.kernel.org, Marcelo Tosatti <marcelo@kvack.org>,
Arjan van de Ven <arjan@infradead.org>,
Martin Bligh <mbligh@google.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andi Kleen <ak@suse.de>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 2/6] Introduce CONFIG_ZONE_DMA
Date: Tue, 19 Sep 2006 00:22:43 +0900 [thread overview]
Message-ID: <20060918152243.GA4320@localhost.na.rta> (raw)
In-Reply-To: <20060918135559.GB15096@infradead.org>
On Mon, Sep 18, 2006 at 02:55:59PM +0100, Christoph Hellwig wrote:
> On Mon, Sep 11, 2006 at 03:27:39PM -0700, Christoph Lameter wrote:
> > Second, arches may use ZONE_DMA in an unknown way. We set CONFIG_ZONE_DMA
> > for all arches that do not set CONFIG_GENERIC_ISA_DMA in order to insure
> > backwards compatibility. The arches may later undefine ZONE_DMA
> > if their arch code has been verified to not depend on ZONE_DMA.
>
> Let's pass this on to linux-arch so that the arch maintainers can give input
> whether they need ZONE_DMA or not. If this just sneaks in unseen I'd bet
> various architectures will just keept it around despite not needing it.
>
sh and sh64 have no use for ZONE_DMA, it's effectively ZONE_DMA ==
ZONE_NORMAL anyways, so it can be safely switched off (though
arch/sh/mm/init.c should then be changed to use ZONE_NORMAL if ZONE_DMA
goes away, as we currently place all lowmem in ZONE_DMA, likewise for
sh64). None of our DMA controllers have any particular limitations where
ZONE_DMA would be useful at least.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Lameter <clameter@sgi.com>,
linux-mm@vger.kernel.org, Nick Piggin <nickpiggin@yahoo.com.au>,
linux-ia64@vger.kernel.org, Marcelo Tosatti <marcelo@kvack.org>,
Arjan van de Ven <arjan@infradead.org>,
Martin Bligh <mbligh@google.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andi Kleen <ak@suse.de>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 2/6] Introduce CONFIG_ZONE_DMA
Date: Mon, 18 Sep 2006 15:22:43 +0000 [thread overview]
Message-ID: <20060918152243.GA4320@localhost.na.rta> (raw)
In-Reply-To: <20060918135559.GB15096@infradead.org>
On Mon, Sep 18, 2006 at 02:55:59PM +0100, Christoph Hellwig wrote:
> On Mon, Sep 11, 2006 at 03:27:39PM -0700, Christoph Lameter wrote:
> > Second, arches may use ZONE_DMA in an unknown way. We set CONFIG_ZONE_DMA
> > for all arches that do not set CONFIG_GENERIC_ISA_DMA in order to insure
> > backwards compatibility. The arches may later undefine ZONE_DMA
> > if their arch code has been verified to not depend on ZONE_DMA.
>
> Let's pass this on to linux-arch so that the arch maintainers can give input
> whether they need ZONE_DMA or not. If this just sneaks in unseen I'd bet
> various architectures will just keept it around despite not needing it.
>
sh and sh64 have no use for ZONE_DMA, it's effectively ZONE_DMA =
ZONE_NORMAL anyways, so it can be safely switched off (though
arch/sh/mm/init.c should then be changed to use ZONE_NORMAL if ZONE_DMA
goes away, as we currently place all lowmem in ZONE_DMA, likewise for
sh64). None of our DMA controllers have any particular limitations where
ZONE_DMA would be useful at least.
next prev parent reply other threads:[~2006-09-18 15:22 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 18:36 [PATCH 0/8] Optional ZONE_DMA V2 Christoph Lameter
2006-09-18 18:36 ` Christoph Lameter
2006-09-11 22:27 ` [PATCH 0/8] Optional ZONE_DMA V1 Christoph Lameter
2006-09-11 22:27 ` [PATCH 2/6] Introduce CONFIG_ZONE_DMA Christoph Lameter
2006-09-18 13:55 ` Christoph Hellwig
2006-09-18 13:55 ` Christoph Hellwig
2006-09-18 14:08 ` Martin Schwidefsky
2006-09-18 14:08 ` Martin Schwidefsky
2006-09-18 17:28 ` Christoph Lameter
2006-09-18 17:28 ` Christoph Lameter
2006-09-19 8:03 ` Martin Schwidefsky
2006-09-19 8:03 ` Martin Schwidefsky
2006-09-18 14:42 ` Russell King
2006-09-18 14:42 ` Russell King
2006-09-18 14:58 ` James Bottomley
2006-09-18 14:58 ` James Bottomley
2006-09-18 17:30 ` Christoph Lameter
2006-09-18 17:30 ` Christoph Lameter
2006-09-18 15:22 ` Paul Mundt [this message]
2006-09-18 15:22 ` Paul Mundt
2006-09-18 17:33 ` Christoph Lameter
2006-09-18 17:33 ` Christoph Lameter
2006-09-18 17:33 ` Christoph Lameter
2006-09-18 22:45 ` Paul Mundt
2006-09-18 22:45 ` Paul Mundt
2006-09-18 22:45 ` Paul Mundt
2006-09-18 22:58 ` Christoph Lameter
2006-09-18 22:58 ` Christoph Lameter
2006-09-18 22:58 ` Christoph Lameter
2006-09-18 23:25 ` Paul Mundt
2006-09-18 23:25 ` Paul Mundt
2006-09-18 23:25 ` Paul Mundt
2006-09-11 22:27 ` [PATCH 3/6] Optional ZONE_DMA in the VM Christoph Lameter
2006-09-12 0:35 ` Nick Piggin
2006-09-12 1:40 ` Christoph Lameter
2006-09-12 1:40 ` Christoph Lameter
2006-09-12 2:40 ` Nick Piggin
2006-09-12 7:22 ` Andi Kleen
2006-09-12 8:30 ` Jes Sorensen
2006-09-12 9:12 ` Jes Sorensen
2006-09-12 18:05 ` Christoph Lameter
2006-09-12 7:30 ` [PATCH 0/8] Optional ZONE_DMA V1 Arjan van de Ven
2006-09-12 13:34 ` Jack Steiner
2006-09-12 17:25 ` Christoph Lameter
2006-09-12 17:33 ` Christoph Lameter
2006-09-12 17:47 ` Martin Bligh
2006-09-12 17:47 ` Martin Bligh
2006-09-12 17:53 ` Christoph Lameter
2006-09-12 17:53 ` Christoph Lameter
2006-09-12 17:40 ` Martin Bligh
2006-09-13 2:41 ` Nick Piggin
2006-09-13 7:55 ` Jes Sorensen
2006-09-13 7:57 ` Jes Sorensen
2006-09-13 8:10 ` Christoph Lameter
2006-09-13 9:52 ` Jes Sorensen
2006-09-13 17:23 ` Christoph Lameter
2006-09-13 17:23 ` Christoph Lameter
2006-09-13 17:49 ` Jack Steiner
2006-09-13 17:49 ` Jack Steiner
2006-09-13 18:00 ` Christoph Lameter
2006-09-13 18:00 ` Christoph Lameter
2006-09-14 8:52 ` Jes Sorensen
2006-09-14 8:52 ` Jes Sorensen
2006-09-14 16:55 ` Christoph Lameter
2006-09-14 16:55 ` Christoph Lameter
2006-09-18 18:36 ` [PATCH 1/8] Deal with cases of ZONE_DMA meaning the first zone Christoph Lameter
2006-09-18 18:36 ` Christoph Lameter
2006-09-18 18:36 ` [PATCH 2/8] Introduce CONFIG_ZONE_DMA Christoph Lameter
2006-09-18 18:36 ` Christoph Lameter
2006-09-18 18:36 ` [PATCH 3/8] Optional ZONE_DMA in the VM Christoph Lameter
2006-09-18 18:36 ` Christoph Lameter
2006-09-18 18:36 ` [PATCH 4/8] Optional ZONE_DMA for i386 Christoph Lameter
2006-09-18 18:36 ` Christoph Lameter
2006-09-18 18:36 ` [PATCH 5/8] Optional ZONE_DMA for x86_64 Christoph Lameter
2006-09-18 18:36 ` Christoph Lameter
2006-09-18 18:36 ` [PATCH 6/8] Optional ZONE_DMA for ia64 Christoph Lameter
2006-09-18 18:36 ` Christoph Lameter
2006-09-18 18:36 ` [PATCH 7/8] Remove ZONE_DMA remains from parisc Christoph Lameter
2006-09-18 18:36 ` Christoph Lameter
2006-09-18 18:36 ` [PATCH 8/8] Remove ZONE_DMA remains from sh/sh64 Christoph Lameter
2006-09-18 18:36 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2006-09-11 22:30 [PATCH 0/8] Optional ZONE_DMA V1 Christoph Lameter
2006-09-11 22:30 ` [PATCH 2/6] Introduce CONFIG_ZONE_DMA 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=20060918152243.GA4320@localhost.na.rta \
--to=lethal@linux-sh.org \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--cc=clameter@sgi.com \
--cc=hch@infradead.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=marcelo@kvack.org \
--cc=mbligh@google.com \
--cc=nickpiggin@yahoo.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.