9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox rsc@plan9.bell-labs.com
Subject: [9fans] PC's 16MB SEGMAPSIZE limitations.
Date: Sat,  1 Aug 1998 15:33:54 -0400	[thread overview]
Message-ID: <19980801193354.E6XKtxELP_2IUB5u-zea2Y4de5jlnNF8AGe8jM8PJTU@z> (raw)

This should be a FAQ.


------ forwarded message follows ------

>From cse.psu.edu!owner-9fans Wed Oct 29 00:48:31 EST 1997
Received: from cse.psu.edu ([130.203.3.50]) by plan9; Wed Oct 29 00:48:31 EST 1997
Received: from localhost (majordom@localhost) by cse.psu.edu (8.8.7/8.7.3) with SMTP id AAA06748; Wed, 29 Oct 1997 00:48:11 -0500 (EST)
Received: by claven.cse.psu.edu (bulk_mailer v1.5); Wed, 29 Oct 1997 00:48:03 -0500
Received: (from majordom@localhost) by cse.psu.edu (8.8.7/8.7.3) id AAA06708 for 9fans-outgoing; Wed, 29 Oct 1997 00:47:57 -0500 (EST)
X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f
Received: from smtp1.fas.harvard.edu (root@smtp1.fas.harvard.edu [140.247.30.81]) by cse.psu.edu (8.8.7/8.7.3) with ESMTP id AAA06704 for <9fans@cse.psu.edu>; Wed, 29 Oct 1997 00:47:53 -0500 (EST)
From: rsc
Received: from p9rsc (rcox.student.harvard.edu [140.247.81.214]) by smtp1.fas.harvard.edu with SMTP id AAA06521; Wed, 29 Oct 1997 00:47:52 -0500 (EST)
Message-Id: <199710290547.AAA06521@smtp1.fas.harvard.edu>
To: cse.psu.edu!9fans
Date: Wed, 29 Oct 1997 00:43:58 -0500
Subject: re: [9fans] How much memory does it require ...
Sender: cse.psu.edu!owner-9fans
Reply-To: cse.psu.edu!9fans
Precedence: bulk

This got tossed around two years ago, and I think the
resolution was that you could change SEGMAPSIZE in pc/mem.h
and all would be fine.  The two attached messages contain
the necessary bits I think.

Nigel Roles said once that 8l uses 20MB to link ghostscript
without any printer drivers.

Russ

--- forwarded messages follow ---
 From cse.psu.edu!9fans-outgoing-owner Thu Nov  2 13:36:19 EST 1995
From:	"G. David Butler" <gdb@dbSystems.com>
To:	9fans@cse.psu.edu
Subject: Re: 386 maximum segment size of 16Mb
Sender: owner-9fans@cse.psu.edu
Reply-To: 9fans@cse.psu.edu

I hate replying to my own mail, but I guess I wasn't finished... :-)

>The real question, has anybody looked into increasing this limit?  (look
>in /sys/src/9/pc/mem.h, SEGMEMSIZE, I think, set to 16.)
Make that                SEGMAPSIZE.

Also several of the machines have this in mem.h:

#define SEGMAPSIZE 64 /* 16 is for wooses */

This would imply that all is necessary is to change 16 to 64 in pc/mem.h,
but that would be too simple...

Thanks again.

 From cse.psu.edu!9fans-outgoing-owner Thu Nov  2 13:59:19 EST 1995
From:	philw@plan9.att.com
To:	9fans@cse.psu.edu
Subject: Re: 386 maximum segment size of 16Mb
Sender: owner-9fans@cse.psu.edu
Reply-To: 9fans@cse.psu.edu


changing SEGMAPSIZE works fine.
It incurs overhead allocated Segment structures
so 16 seemed reasonable for a terminal. We really
dont use PC's to compile.




             reply	other threads:[~1998-08-01 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-01 19:33 Russ [this message]
1998-08-01 19:54 dina
1998-08-01 20:27 jmk
1998-08-01 22:47 Erik
1998-08-03  9:54 forsyth
1998-08-04 22:15 Erik

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=19980801193354.E6XKtxELP_2IUB5u-zea2Y4de5jlnNF8AGe8jM8PJTU@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).