9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rsc@plan9.bell-labs.com rsc@plan9.bell-labs.com
Subject: [9fans] How much memory does it require ...
Date: Wed, 29 Oct 1997 00:43:58 -0500	[thread overview]
Message-ID: <19971029054358.p3IRSGZ4UaR-BuZlqkoNW8hfBVDYPJ9HZDwpmUlQ0eY@z> (raw)

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:[~1997-10-29  5:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-29  5:43 rsc [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-10-29  5:38 Scott
1997-10-29  5:27 Kenji

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=19971029054358.p3IRSGZ4UaR-BuZlqkoNW8hfBVDYPJ9HZDwpmUlQ0eY@z \
    --to=rsc@plan9.bell-labs.com \
    /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).