Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ames!ucsd!ncr-sd!falstaf!kit
From: kit@falstaf.SanDiego.NCR.COM (Kit Chow)
Newsgroups: comp.unix.wizards
Subject: kernel questions
Message-ID: <885@ncr-sd.SanDiego.NCR.COM>
Date: 14 Feb 89 18:05:22 GMT
Sender: news@ncr-sd.SanDiego.NCR.COM
Reply-To: kit@falstaf.SanDiego.NCR.COM (Kit Chow, x3039)
Distribution: usa
Organization: NCR Corporation, Rancho Bernardo
Lines: 9

1) If a user process can be 'nailed' into memory, is there still a
need to copyin(k) data from user virtual address space into kernel
address space? If no, could the kernel then access the user data
in the user virtual address space with minimum overhead?

2) What exactly does wakeup(k) do to move processes from the
SLEEP state to the READY state? Is there a different linked list
of SLEEPing and READY processes? If no, does the scheduler traverse
through the entire proc array to find the next READY process to run?