From: BenHanokh Gabriel <gabriel@SANgate.com>
To: linux-mm@kvack.org
Subject: max memory limits ???
Date: Wed, 22 Nov 2000 15:37:09 +0200 [thread overview]
Message-ID: <3A1BCC05.4080608@SANgate.com> (raw)
hi
can some1 explain the memory limits on the 2.4 kernel
- what is the maximum amount of physical memory it supports ?
- what is the limit for user-space apps ?
- what is the limit for kernel ?
- are there any limits on malloc, static-memory, stack-memory ?
- does using HIGHMEM results with performance penalty ?
- anything else ?
please CC me for any answer
regards
Benhanokh Gabriel
-----------------------------------------------------------------------------
"If you think C++ is not overly complicated, just what is a
protected abstract virtual base class with a pure virtual private destructor,
and when was the last time you needed one?"
-- Tom Cargil, C++ Journal, Fall 1990. --
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next reply other threads:[~2000-11-22 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 13:37 BenHanokh Gabriel [this message]
2000-11-22 14:11 ` Matti Aarnio
2000-11-22 15:28 ` Stephen C. Tweedie
2000-11-25 10:45 ` Raymond Nijssen
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=3A1BCC05.4080608@SANgate.com \
--to=gabriel@sangate.com \
--cc=linux-mm@kvack.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