Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!purdue!ames!lll-lcc!lll-winken!uunet!convex!killer!walls
From: walls@killer.Dallas.TX.US (Monty Walls)
Newsgroups: comp.os.minix
Subject: shared code segments, multi-tasking
Keywords: pure code shared
Message-ID: <8024@killer.Dallas.TX.US>
Date: 6 May 89 03:38:48 GMT
Organization: The Unix(R) Connection, Dallas, Texas
Lines: 24


--------------------------------------------------------------------------
	One method people might consider is using shared text segments.
Since most of the reason to use swapping is running out of memory while
doing a 'make' in the background while editing, the shared text segments
will free up 30k+ memory reasonably simply.  
	The changes to use shared code segments should all be 
confined to the MM and resonable simple.  I am assuming that the ACK
C compiler is segment aligning the starting point for the data space
in i+d mode.
	To improve the multi-tasking behavior when you are running
multiple tasks you might consider changing the size of a processor
time-slice.  I'm using MILLISEC defined as 40 in kernel/clock.c on a 
8mhz AT.  This seems to give a decent response time when using multiple
tasks.

	-Monty Walls
Work:						Home:
	MIS Division, Tech. Support			2224 Houston Apt #8
	Oklahoma Tax Commission				Norman, OK, 73701
	2501 N. Lincoln					USA
	OKC, OK, 73194 					Phone - 405-364-5123
	USA						uucp - killer!walls
	Phone - 405-521-4300