Thread View: comp.sys.sequent
2 messages
2 total messages
Started by Peter Eriksson
Mon, 21 May 1990 18:44
16MB limit in Dynix 2.1.1
Author: Peter Eriksson
Date: Mon, 21 May 1990 18:44
Date: Mon, 21 May 1990 18:44
13 lines
1082 bytes
1082 bytes
Is it possible to change any parameter and rebuild the Dynix 2.1.1 kernel so that the 16MB user memory limit can be set to 256MB? We're having some trouble with gcc getting a "virtual memory exhausted" error when doing an optimized compile on some of it's large sources... The machine is a Balance 8000, with 12 cpu:s and 10MB of memory. Peter Eriksson -- Peter Eriksson pen@lysator.liu.se Lysator Computer Club ...!uunet!lysator.liu.se!pen University of Linkoping, Sweden "Seize the day!"
Re: 16MB limit in Dynix 2.1.1
Author: Ian Johnstone
Date: Sat, 26 May 1990 18:41
Date: Sat, 26 May 1990 18:41
16 lines
1040 bytes
1040 bytes
In article <24@lysator.liu.se> pen@lysator.liu.se (Peter Eriksson) writes: > >Is it possible to change any parameter and rebuild the Dynix 2.1.1 >kernel so that the 16MB user memory limit can be set to 256MB? We're >having some trouble with gcc getting a "virtual memory exhausted" error >when doing an optimized compile on some of it's large sources... > >The machine is a Balance 8000, with 12 cpu:s and 10MB of memory. > Peter the limitation isn't with the OS it is with the NS32032 chipset that is used in hte balance series. -- Ian Johnstone uunet!sequent!ianj Sequent Computer Systems 503-626-5700 Beaverton, Oregon
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads