home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!howland.reston.ans.net!spool.mu.edu!agate!doc.ic.ac.uk!uknet!yorkohm!minster!forsyth
- From: forsyth@minster.york.ac.uk
- Newsgroups: comp.unix.aix
- Subject: re: process numbers
- Message-ID: <726871523.17488@minster.york.ac.uk>
- Date: 12 Jan 93 20:45:24 GMT
- Organization: Department of Computer Science, University of York, England
- Lines: 14
-
- making a process ID a function of its index in a process table
- (or equivalent) speeds creation of unique process IDs:
- instead of searching the proc. table, or having lots of code
- to keep track of unique ranges (cf. bsd), fork simply takes the previous process ID
- in that slot and adds NPROC (or equivalent),
- with a line or two to deal with overflow.
- as someone noted, this process ID representation also simplifies finding a Proc structure
- given a process ID.
- other unique IDs can be handled in a similar way.
-
- the Waterloo Thoth system was an early user of a similar scheme,
- although I don't think it was a new idea even then.
- it's the first time i've seen `security hole' as a justification
- for its use, though!
-