From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: make CONFIG_ZONE_DMA user settable
Date: Tue, 24 Jun 2014 15:14:55 +0100 [thread overview]
Message-ID: <20140624141455.GE4489@arm.com> (raw)
In-Reply-To: <1403529423.755.49.camel@deneb.redhat.com>
On Mon, Jun 23, 2014 at 02:17:03PM +0100, Mark Salter wrote:
> On Mon, 2014-06-23 at 12:09 +0100, Catalin Marinas wrote:
> > My proposal (in the absence of any kind of description) is to still
> > create a ZONE_DMA if we have DMA memory below 32-bit, otherwise just add
> > everything (>32-bit) to ZONE_DMA. Basically an extension from your CMA
> > patch, make dma_phys_limit static in that file and set it to
> > memblock_end_of_DRAM() if no 32-bit DMA. Re-use it in the
> > zone_sizes_init() function for ZONE_DMA (maybe with a pr_info for no
> > 32-bit only DMA zone).
>
> There's a performance issue with all memory being in ZONE_DMA. It means
> all normal allocations will fail on ZONE_NORMAL and then have to fall
> back to ZONE_DMA. It would be better to put some percentage of memory
> in ZONE_DMA.
Is the performance penalty real or just theoretical? I haven't run any
benchmarks myself.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Salter <msalter@redhat.com>
Cc: Will Deacon <Will.Deacon@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: make CONFIG_ZONE_DMA user settable
Date: Tue, 24 Jun 2014 15:14:55 +0100 [thread overview]
Message-ID: <20140624141455.GE4489@arm.com> (raw)
In-Reply-To: <1403529423.755.49.camel@deneb.redhat.com>
On Mon, Jun 23, 2014 at 02:17:03PM +0100, Mark Salter wrote:
> On Mon, 2014-06-23 at 12:09 +0100, Catalin Marinas wrote:
> > My proposal (in the absence of any kind of description) is to still
> > create a ZONE_DMA if we have DMA memory below 32-bit, otherwise just add
> > everything (>32-bit) to ZONE_DMA. Basically an extension from your CMA
> > patch, make dma_phys_limit static in that file and set it to
> > memblock_end_of_DRAM() if no 32-bit DMA. Re-use it in the
> > zone_sizes_init() function for ZONE_DMA (maybe with a pr_info for no
> > 32-bit only DMA zone).
>
> There's a performance issue with all memory being in ZONE_DMA. It means
> all normal allocations will fail on ZONE_NORMAL and then have to fall
> back to ZONE_DMA. It would be better to put some percentage of memory
> in ZONE_DMA.
Is the performance penalty real or just theoretical? I haven't run any
benchmarks myself.
--
Catalin
next prev parent reply other threads:[~2014-06-24 14:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 5:05 [PATCH] arm64: make CONFIG_ZONE_DMA user settable Mark Salter
2014-06-23 5:05 ` Mark Salter
2014-06-23 9:01 ` Russell King - ARM Linux
2014-06-23 9:01 ` Russell King - ARM Linux
2014-06-23 11:09 ` Catalin Marinas
2014-06-23 11:09 ` Catalin Marinas
2014-06-23 13:17 ` Mark Salter
2014-06-23 13:17 ` Mark Salter
2014-06-24 14:14 ` Catalin Marinas [this message]
2014-06-24 14:14 ` Catalin Marinas
2014-06-24 14:38 ` Mark Salter
2014-06-24 14:38 ` Mark Salter
2014-07-18 11:07 ` Catalin Marinas
2014-07-18 11:07 ` Catalin Marinas
2014-07-18 11:58 ` Anup Patel
2014-07-18 11:58 ` Anup Patel
2014-07-18 14:59 ` Catalin Marinas
2014-07-18 14:59 ` Catalin Marinas
2014-07-21 21:56 ` Mark Salter
2014-07-21 21:56 ` Mark Salter
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=20140624141455.GE4489@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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.