From: Catalin Marinas <catalin.marinas@gmail.com>
To: Bas Vermeulen <bvermeul@blackstar.xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NOMMU - How to reserve 1 MB in top of memory in a clean way
Date: Wed, 06 Apr 2005 16:56:34 +0100 [thread overview]
Message-ID: <tnxd5t7aogd.fsf@arm.com> (raw)
In-Reply-To: <1112800564.2687.40.camel@laptop.blackstar.nl> (Bas Vermeulen's message of "Wed, 06 Apr 2005 17:16:04 +0200")
Bas Vermeulen <bvermeul@blackstar.xs4all.nl> wrote:
> This will put me in the zone of 'it ain't ever going to be integrated'.
> I'd preferrably find a solution without changing the zones. My ideal
> solution would be grabbing pages before they are assigned to a zone, or
> at least for the zone to recognize them as used.
The order of the zones was initially chosen based on x86 and ISA
bus. This is no longer valid for all the platforms (for example, the
1st MB can be SSRAM and not usable for DMA).
This might be possible but I've never tried (and not sure how it would
work with nommu) - define CONFIG_NUMA and use 2 memory banks, one from
0 to max - 1M and the 2nd being 1MB. You can define the zone sizes for
each node when calling free_area_init_node() so that the first node
doesn't have any DMA area and the 2nd one has only DMA.
Maybe other could comment on this, not sure it will work. What core
are you using?
A third option could be to define your own dma_alloc* functions and
not give the top MB to the kernel (mem=...).
--
Catalin
prev parent reply other threads:[~2005-04-06 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 9:50 NOMMU - How to reserve 1 MB in top of memory in a clean way Bas Vermeulen
2005-04-06 13:26 ` Catalin Marinas
2005-04-06 14:53 ` Richard B. Johnson
2005-04-06 15:05 ` Catalin Marinas
2005-04-06 15:13 ` Bas Vermeulen
2005-04-06 15:16 ` Bas Vermeulen
2005-04-06 15:56 ` Catalin Marinas [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=tnxd5t7aogd.fsf@arm.com \
--to=catalin.marinas@gmail.com \
--cc=bvermeul@blackstar.xs4all.nl \
--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