【正文】 () or waitpid().Another name for a process is a task. The Linux kernel internally refers to processes as tasks. although when I say task I am generally referring to a process from the kernel39。__s32 preempt_count。s actual task_struct.3 Storing the Process DescriptorThe system identifies processes by a unique process identification value or PID. The PID is a numerical value that is represented by the opaque type pid_t, which is typically an int. Because of backward patibility with earlier Unix and Linux versions, however, the default maximum value is only 32,768 although the value can optionally be increased to the full range afforded the type. The kernel stores this value as pid inside each process descriptor.This maximum value is important because it is essentially the maximum number of processes that may exist concurrently on the system. Although 32,768 might be sufficient for a desktop system, large servers may require many more processes. The lower 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 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, %eaxandl %esp, %eaxThis 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。s state. The preferred mechanism is using set_task_state(task, state)。 執(zhí)行線程，簡(jiǎn)稱線程（thread），是在進(jìn)程中活動(dòng)的對(duì)象。而虛擬內(nèi)存讓進(jìn)程在獲取和使用內(nèi)存是覺得自己擁有整個(gè)操作系統(tǒng)的所有內(nèi)存資源。在調(diào)用結(jié)束的時(shí)，在返回這個(gè)相同位置上，父進(jìn)程恢復(fù)執(zhí)行，子進(jìn)程開始執(zhí)行。 進(jìn)程的另一個(gè)名字是任務(wù)（task）。進(jìn)程描述符中包含的數(shù)據(jù)能完整的描述一個(gè)正在執(zhí)行的程序：它打開的文件，進(jìn)程的地址空間，掛起的信號(hào)，進(jìn)程的狀態(tài)，還有其他更多的信息。 Unsigned long flags。}每個(gè)任務(wù)的thread_info 結(jié)構(gòu)在它的內(nèi)核棧的尾端分配。這個(gè)值越小，轉(zhuǎn)一圈就越快，本類數(shù)值大的進(jìn)程比數(shù)值小的進(jìn)程遲運(yùn)行，但這樣一來就破壞了這一原則。在x86體系上，current把棧指針的后13個(gè)有效位屏蔽掉，用來計(jì)算出thread_info的偏移。而訪問進(jìn)程描述符是一個(gè)重要的頻繁的操作，所以PPC的內(nèi)核開發(fā)者會(huì)覺得完全有必要為此使用一個(gè)專門的寄存器。（3） TASK_UNINTERRUPTIBLE（不可中斷）——除了不會(huì)因?yàn)榻邮艿叫盘?hào)而被喚醒從而投入運(yùn)行外，這個(gè)狀態(tài)與可打斷的狀態(tài)相同。5 設(shè)置當(dāng)前進(jìn)程狀態(tài)內(nèi)核經(jīng)常需要調(diào)整某個(gè)進(jìn)程的狀態(tài)。一般程序在用戶空間