From: Tom Rini <trini@kernel.crashing.org>
To: "David C. Chiu" <dchiu@ariodata.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Memory Pre-allocation (mem=xxx)
Date: Sat, 23 Feb 2002 17:15:04 -0700 [thread overview]
Message-ID: <20020224001504.GA19685@opus.bloom.county> (raw)
In-Reply-To: <20020223171400.GA18617@opus.bloom.county>
On Sat, Feb 23, 2002 at 10:14:00AM -0700, Tom Rini wrote:
>
> On Fri, Feb 22, 2002 at 07:11:00PM -0800, David C. Chiu wrote:
>
> > Thanks for the response. Would you be so kind to be more specific? I did
> > a coarse search of the kernel documentation subdirectory contents, but
> > fail to find what you are referring to (although I have been referred to
> > as the seeing blind in the past.)
>
> Sorry, I don't recall exactly where/what it is. I do remember there
> being a few projects which required a large chunk of contigious memory,
> and having to do mem=XXm in 2.0 (2.2?) but in 2.2 (2.4?) there's kernel
> calls you can make to get a large contig section of memory, if it
> exists.
... and it might even be the 'alloc_bootmem' call Jim Lewis mentioned,
now that I think about it..
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-24 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 3:11 Memory Pre-allocation (mem=xxx) David C. Chiu
2002-02-23 17:14 ` Tom Rini
2002-02-24 0:15 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 21:23 David C. Chiu
2002-02-23 1:21 David C. Chiu
2002-02-25 12:35 ` Kenneth Johansson
2002-02-23 0:42 David C. Chiu
2002-02-23 0:57 ` Wolfgang Denk
2002-02-23 1:54 ` Jim Lewis
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=20020224001504.GA19685@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=dchiu@ariodata.com \
--cc=linuxppc-embedded@lists.linuxppc.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