In fact, I haven't figured out the relationship between Process and Thread. Because I don't have THREAD's concept in the Linux version now, I looked at it in these two days, and the Thread under Windows is actually very similar. They are all scheduling minimal units. Under Windows, Process only provides process for CONTEXT and other variables, and there is a paragraph in Inside Windows 2000. Clear:
As already noted, Windows 2000 schedules at the thread granularity. This approach makes sense when you consider that processes do not run but only provide resources and a context in which their threads run. Because scheduling decisions are made strictly on a thread basis, no consideration is given to what process the thread belongs to. For example, if process A has 10 runnable threads and process B has 2 runnable threads, and all 12 threads are at the same priority, each thread would receive one-twelfth of the CPU time -Windows 2000 Wouldn't Give 50 Percent of The CPU to Process A and 50 Per
Thread under Windows does not have its own address space, it is the same as the other Thread public in this process, but each Thread is your own kernel stack, and there should be USER Stack ,,,, Linux2.6 The kernel thread can also be seized, and the windwos can be
