Lines Matching refs:P
197 a process PP which accessing a Coda file. It makes a system call which
272 on behalf of a process P, creates messages for Venus, awaits replies
276 FS Driver in kernel memory on behalf of P and copied to user memory in
279 The FS Driver while servicing P makes upcalls to Venus. Such an
281 structure contains the identification of P, the message sequence
296 P. When the message is on the pending queue, process P cannot proceed
297 in upcall. The (kernel mode) processing of P in the filesystem
299 the calling thread in P is blocked in upcall. A pointer in the
300 message structure will locate the synchronization object on which P is
315 +o the message is a reply for a suspended thread P. If so it removes
317 WRITTEN. Finally, the FS driver unblocks P (still in the kernel
319 Venus. The process P will be scheduled at some point and continues
328 Now P awakes and continues processing upcall. There are some
329 subtleties to take account of. First P will determine if it was woken
331 attempt to terminate P) or as is normally the case by Venus in its
344 In case P is woken up by a signal and not by Venus, it will first look
345 at the flags field. If the message is not yet READ, the process P can
347 the request should not be processed, P can send Venus a signal message
364 file descriptor for the device. The process P is kept waiting on an
372 message arrival. The process P is kept waiting on a KernelEvent
1486 55..33.. PPUURRGGEEUUSSEERR
1555 55..77.. PPUURRGGEEFFIIDD