From: Erik Theisen etheisen@mindspring.com
Subject: [9fans] PC's 16MB SEGMAPSIZE limitations.
Date: Sat, 1 Aug 1998 18:47:00 -0400 [thread overview]
Message-ID: <19980801224700.m9roV4zeRFwJ3XwslDI3UwTpX2SHmd-6OYuYnG-XmbU@z> (raw)
After applying all the AT&T updates to "Plan 9", I tried to rebuild the
world. Several items refused to compile due to "out of mem"
conditions, namely some of the larger things in libtiff.
After digging around, I see that the maximum segment size is 16MB for
PCs (mem.h - SEGMAPSIZE). This would explain the behavior I'm seeing
out of the 8c compiler as it uses sbrk to extend its BSS segment up to
16MB before it dies.
I tried bumping SEGMAPSIZE to 64 and the machine became unstable. Seems
there are other hard coded limits throughout the Plan 9 PC kernel, 16,
64, 128 etc. It appears that the maximum process footprint is limited
to 64MB. This is a truly sad condition for modern machines.
Has anyone had luck getting the 9 PC kernel out of the 16MB gear?
Ciao,
Erik
next reply other threads:[~1998-08-01 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-01 22:47 Erik [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-08-04 22:15 Erik
1998-08-03 9:54 forsyth
1998-08-01 20:27 jmk
1998-08-01 19:54 dina
1998-08-01 19:33 Russ
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=19980801224700.m9roV4zeRFwJ3XwslDI3UwTpX2SHmd-6OYuYnG-XmbU@z \
--to=9fans@9fans.net \
/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).