SUBSTANTIAL INFORMATION ABOUT THREAD OF ATLEAST THREE OS Posted by ELIEZER
11:00 PM Posted In OS-6 Edit This 0 Comments »Windows Server 2008
Kernel improvements are significant because the kernel provides
- low-level operating system functions,
- including thread scheduling,
- interrupt and exception dispatching,
- multiprocessor synchronization, and
- a set of routines and basic objects that the rest of the operating system uses to implement higher-level constructs.
WINDOWS XP THREAD
Implements the one-to-one mapping
Each thread contains
-> A thread id
-> Register set
-> Separate user and kernel stacks
-> Private data storage area
The register set, stacks, and private storage area are known as the context of the threads
The primary data structures of a thread include:
-> ETHREAD (executive thread block)
-> KTHREAD (kernel thread block)
-> TEB (thread environment block)
WINDOWS NT’s Threads
- Primary thread - When a process is created, one thread is generated along with it.
This object is then scheduled on a system wide basis by the kernel to execute on a processor.
After the primary thread has started, it can create other threads that share its address space and system resources but have independent contexts, which include execution stacks and thread specific data. A thread can execute any part of a process' code, including a part currently being executed by another thread.
It is through threads, provided in the Win32 application programmer interface (API), that Windows NT allows programmers to exploit the benefits of concurrency and parallelism.
- Fiber - is NT’s smallest user-level object of execution. It executes in the context of a thread and is unknown to the operating system kernel. A thread can consist of one or more fibers as determined by the application programmer. ˝Some literature ˝[1,11] assume that there is a one-to-one mapping of userlevel objects to kernel-level objects, this is inaccurate. Windows NT does ˝provide the means for many-to-many ˝scheduling. However, NT's design is poorly documented and the application programmer is responsible for the control of fibers such as allocating memory, scheduling them on threads and preemption.
0 comments:
Post a Comment