From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: how can I cleanly exclude memory from the kernel memory allocator?
Date: Fri, 25 Mar 2011 20:27:55 +0000 [thread overview]
Message-ID: <20110325202755.GA13574@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110325173928.GD29359@labbmf-linux.qualcomm.com>
On Fri, Mar 25, 2011 at 10:39:28AM -0700, Larry Bassel wrote:
> OK, please ignore my previous mail, I see that .fixup can be
> used to adjust tags. It appears to me, however, that using a
> .reserve function calling memblock_reserve will be an
> easier way of doing what I need.
Absolutely.
next prev parent reply other threads:[~2011-03-25 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 22:18 how can I cleanly exclude memory from the kernel memory allocator? Larry Bassel
2011-03-24 23:14 ` Colin Cross
2011-03-25 17:37 ` Larry Bassel
2011-03-24 23:27 ` Nicolas Pitre
2011-03-25 15:28 ` Larry Bassel
2011-03-25 17:39 ` Larry Bassel
2011-03-25 20:27 ` Russell King - ARM Linux [this message]
2011-04-19 23:33 ` Larry Bassel
2011-04-19 23:40 ` Larry Bassel
2011-04-20 6:48 ` Colin Cross
2011-04-20 19:22 ` Larry Bassel
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=20110325202755.GA13574@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).