Message from discussion
What would you like to see most in minix?
Path: gmdzi!unido!mcsun!news.funet.fi!hydra!klaava!torvalds
From: torva...@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: comp.os.minix
Subject: Re: What would you like to see most in minix?
Keywords: 386, preferences
Message-ID: <1991Aug28.105619.16056@klaava.Helsinki.FI>
Date: 28 Aug 91 10:56:19 GMT
References: <1991Aug25.234450.22562@nntp.hut.fi> <1991Aug26.110602.19446@klaava.Helsinki.FI> <1991Aug27.143432.10473@ukpoit.co.uk>
Organization: University of Helsinki
Lines: 18
In article <1991Aug27.143432.10...@ukpoit.co.uk> a...@ukpoit.co.uk (Alan Barclay) writes:
>In article <1991Aug26.110602.19...@klaava.Helsinki.FI> torva...@klaava.Helsinki.FI (Linus Benedict Torvalds) writes:
>>yet) and segmentation. It's the segmentation that makes it REALLY 386
>>dependent (every task has a 64Mb segment for code & data - max 64 tasks
>>in 4Gb. Anybody who needs more than 64Mb/task - tough cookies).
>>
>
>Is that max 64 64Mb tasks or max 64 tasks no matter what their size?
I'm afraid that is 64 tasks max (and one is used as swapper), no matter
how small they should be. Fragmentation is evil - this is how it was
handled. As the current opinion seems to be that 64 Mb is more than
enough, but 64 tasks might be a little crowded, I'll probably change the
limits be easily changed (to 32Mb/128 tasks for example) with just a
recompilation of the kernel. I don't want to be on the machine when
someone is spawning >64 processes, though :-)
Linus