【文章內(nèi)容簡(jiǎn)介】 r the value, the sooner the values will wrap around, destroying the useful notion that higher values indicate later run processes than lower values. If the system is willing to break patibility with old XXX 工業(yè)大學(xué)本科畢業(yè)設(shè)計(jì)外文文獻(xiàn)翻譯 4 applications, the administrator may increase the maximum value via /proc/sys/kernel/pid_max. Inside the kernel, tasks are typically referenced directly by a pointer to their task_struct structure. In fact, most kernel code that deals with processes works directly with struct task_struct. Consequently, it is very useful to be able to quickly look up the process descriptor of the currently executing task, which is done via the current macro. This macro must be separately implemented by each architecture. Some architectures save a pointer to the task_struct structure of the currently running process in a register, allowing for efficient access. Other architectures, such as x86 (which has few registers to waste), make use of the fact that struct thread_info is stored on the kernel stack to calculate the location of thread_info and subsequently the task_struct. On x86, current is calculated by masking out the 13 least significant bits of the stack pointer to obtain the thread_info structure. This is done by the current_thread_info() function. The assembly is shown here: movl $8192, %eax andl %esp, %eax This assumes that the stack size is 8KB. When 4KB stacks are enabled, 4096 is used in lieu of 8192. Finally, current dereferences the task member of thread_info to return the task_struct:current_thread_info()task。 Contrast this approach with that taken by PowerPC (IBM39。s modern RISCbased microprocessor), which stores the current task_struct in a register. Thus, current on PPC merely returns the value stored in the register r2. PPC can take this approach because, unlike x86, it has plenty of registers. Because accessing the process descriptor is a mon and important job, the PPC kernel developers deem using a register worthy for the task. 4 Process State The state field of the process descriptor describes the current condition of the process. Each process on the system is in exactly one of five different states. This value is represented by one of five flags: XXX 工業(yè)大學(xué)本科畢業(yè)設(shè)計(jì)外文文獻(xiàn)翻譯 5 (1) TASK_RUNNING The process is runnable。 it is either currently running or on a runqueue waiting to run. This is the only possible state for a process executing in userspace。 it can also apply to a process in kernelspace that is actively running. (2) TASK_INTERRUPTIBLE. The process is sleeping (that is, it is blocked), waiting for some condition to exist. When this condition exists, the kernel sets the process39。s state to TASK_RUNNING. The process also awakes prematurely and bees runnable if it receives a signal. (3) TASK_UNINTERRUPTIBLE This state is identical to TASK_INTERRUPTIBLE except that it does not wake up and bee runnable if it receives a signal. This is used in situations where the process must wait without interruption or when the event is expected to occur quite quickly. Because the task does not respond to signals in this state, this state is less often used than TASK_INTERRUPTIBLE (4)TASK_ZOMBIE The task has terminated, but its parent has not yet iss