From: Borislav Petkov <bp@alien8.de>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, rientjes@google.com, hpa@linux.intel.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/mm] x86, mm: Allow ZONE_DMA to be configurable
Date: Wed, 17 Aug 2011 12:37:17 +0200 [thread overview]
Message-ID: <20110817103717.GA5172@liondog.tnic> (raw)
In-Reply-To: <tip-dc382fd5bcca7098a984705ed6ac880f539d068e@git.kernel.org>
On Mon, May 16, 2011 at 11:13:07PM +0000, tip-bot for David Rientjes wrote:
> Commit-ID: dc382fd5bcca7098a984705ed6ac880f539d068e
> Gitweb: http://git.kernel.org/tip/dc382fd5bcca7098a984705ed6ac880f539d068e
> Author: David Rientjes <rientjes@google.com>
> AuthorDate: Mon, 16 May 2011 13:54:10 -0700
> Committer: H. Peter Anvin <hpa@linux.intel.com>
> CommitDate: Mon, 16 May 2011 14:03:28 -0700
>
> x86, mm: Allow ZONE_DMA to be configurable
>
> ZONE_DMA is unnecessary for a large number of machines that do not
> require less than 32-bit DMA addressing, e.g. ISA legacy DMA or PCI
> cards with a restricted DMA address mask.
>
> This patch allows users to disable ZONE_DMA for x86 if they know they
> will not be using such devices with their kernel.
>
> This prevents the VM from unnecessarily reserving a ratio of memory
> (defaulting to 1/256th of system capacity) with lowmem_reserve_ratio
> for such allocations when it will never be used.
>
> Signed-off-by: David Rientjes <rientjes@google.com>
> Link: http://lkml.kernel.org/r/alpine.DEB.2.00.1105161353560.4353@chino.kir.corp.google.com
> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
This causes the ZONE_DMA menu option to appear in the toplevel menu of
the kernel configurator instead of under EXPERT, where it should belong
IMO.
> ---
> arch/x86/Kconfig | 9 ++++++++-
> arch/x86/mm/init_32.c | 2 ++
> arch/x86/mm/init_64.c | 2 ++
> 3 files changed, 12 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 648fca4..0eb801a 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -112,7 +112,14 @@ config MMU
> def_bool y
>
> config ZONE_DMA
> - def_bool y
> + bool "DMA memory allocation support" if EXPERT
> + default y
> + help
> + DMA memory allocation support allows devices with less than 32-bit
> + addressing to allocate within the first 16MB of address space.
> + Disable if no such devices will be used.
> +
> + If unsure, say Y.
maybe this should go into init/Kconfig ?
Thanks.
--
Regards/Gruss,
Boris.
prev parent reply other threads:[~2011-08-17 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 18:38 [patch v2] x86: allow " David Rientjes
2011-04-15 11:42 ` Clemens Ladisch
2011-04-15 20:08 ` H. Peter Anvin
2011-04-21 2:31 ` David Rientjes
2011-04-21 4:07 ` H. Peter Anvin
2011-04-27 23:37 ` [patch v3] " David Rientjes
2011-05-04 0:00 ` David Rientjes
2011-05-04 0:20 ` H. Peter Anvin
2011-05-16 20:54 ` [patch v4] " David Rientjes
2011-05-16 20:56 ` H. Peter Anvin
2011-05-16 23:13 ` [tip:x86/mm] x86, mm: Allow " tip-bot for David Rientjes
2011-08-17 10:37 ` Borislav Petkov [this message]
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=20110817103717.GA5172@liondog.tnic \
--to=bp@alien8.de \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®