From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Petko Manolov <petkan@varel.bg>
Cc: linux-mm@kvack.org
Subject: Re: May be stupid question ;-)
Date: Fri, 13 Nov 1998 15:12:36 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.3.96.981113150452.4593A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <364C2049.360B6131@varel.bg>
On Fri, 13 Nov 1998, Petko Manolov wrote:
> I'm wonder if its possible to have kernel code+data > 4M?
Currently not, unless you compile in all sorts of useless
drivers (or you have a machine with 30+ different kinds of
extension cards)...
> So pg0 won't be enough. And we have to init pg1. AFAIK the kernel
> don't allocate more page tables for itself while in run. It sounds
> to me like troubles in the future.
Most of the runtime tables are allocated after the memory
stuff has been taken care off. Then we have the infrastructure
to allocate as much memory as we want without problems.
Rik -- slowly getting used to dvorak kbd layout...
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-11-13 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-13 12:04 Petko Manolov
1998-11-13 14:12 ` Rik van Riel [this message]
1998-11-16 7:44 ` Petko Manolov
1998-11-16 8:30 ` 4M kernel pages Petko Manolov
[not found] ` <wd8emr3yfeu.fsf@parate.irisa.fr>
1998-11-16 15:06 ` Petko Manolov
1998-11-16 15:27 ` David Mentr\'e
1998-11-16 16:50 ` Petko Manolov
1998-11-16 18:18 ` David Mentr\'e
1998-11-17 9:30 ` Petko Manolov
1998-11-16 18:43 ` Rik van Riel
1998-11-17 9:34 ` Petko Manolov
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=Pine.LNX.3.96.981113150452.4593A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=linux-mm@kvack.org \
--cc=petkan@varel.bg \
/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