Thread View: mod.computers.68k
1 messages
1 total messages
Started by bsteve
Sat, 14 Mar 1987 15:35
Re: forking around - final word on microtoys.
Author: bsteve
Date: Sat, 14 Mar 1987 15:35
Date: Sat, 14 Mar 1987 15:35
33 lines
1688 bytes
1688 bytes
/* Bandygram for Mister Mongo... */
In article <8703080916.AA12728@gorgo.att.com> I wrote:
>Hardly impossible.
>You have to do some dynamic relocation in order to make this work. This
>means keeping some of the original linking information around. It isn't
>really too much to pay.
/* Bandy hits! */
>You're not paying attention. What about pointers to data that you have
>malloc()ed? You're either going to need an MMU (==data space relocation) or
>you're going to need to swap the data space around.
What I really meant was that you could do it. There are severe limitations
likely to be placed on the child process regarding what data sticks around.
There are actually ways to get around this, but they all generate lots of
overhead. We would prefer that forks take less than 20 ms.
/* Bandy hits again! -more- */
>This is why 68ks w/o MMUs (data and program relocation) are toy computers.
Agreed.
> Enough already, people!
Further agreed.
Steve Blasingame (Oklahoma City)
ihnp4!occrsh!gorgo!bsteve
bsteve@eris.berkeley.edu
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