home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.minix
- Path: sparky!uunet!mcsun!sun4nl!relay.philips.nl!philica!adrie
- From: adrie@ica.philips.nl (Adrie Koolen)
- Subject: Re: Microkernel discussion
- Message-ID: <1992Jul22.072333.1552@ica.philips.nl>
- Organization: Philips Consumer Electronics, Eindhoven, The Netherlands
- References: <1992Jul21.093145.328@ica.philips.nl> <1992Jul21.135917.3527@philce.ce.philips.nl>
- Date: Wed, 22 Jul 1992 07:23:33 GMT
- Lines: 27
-
- In article <1992Jul21.135917.3527@philce.ce.philips.nl> meulenbr@ce.philips.nl (Frans Meulenbroeks) writes:
- >Also the situation where a driver dies is quite rare (but of course it
- >can occur). For the time being I decided just to ignore this case.
-
- I think that it's not quite rare. The mechanism you're proposing, helps
- to easily reinstall drivers in a running system. When you do, a driver
- can (and often will) be put in a different process slot. We should
- cover this case.
-
- Also, although I agree that it takes a lot of time to search for a name
- in the process table, things might be not that bad if you use a binary
- search method or a hash table. Furthermore, user processes can sendrec
- only to/from the MM and FS (or a limited number of other server
- processes), so one should have a very small number of processes to
- check for when a user process sends a message.
-
- >In due time this could be solved by redefining the address to which
- >the data is sent. I can imagine that the address consists of e.g.
- >proc no. + pid or proc no + name, and that send checks if the
- >address is still valid. If not an error could be returned, and the
- >caller can check if there is another new process registered under that
- >name and rework the address.
-
- Good idea. That keeps the speed (but adds parameters).
-
- Adrie Koolen (adrie@ica.philips.nl)
- Philips Consumer Electronics, Eindhoven, the Netherlands
-