Size: 552
Comment:
|
Size: 883
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
Parent Node : [:KernelHacking-HOWTO:KernelHacking-HOWTO] |
|
Line 3: | Line 5: |
1. Processes 1. [:KernelHacking-HOWTO/Subsystems/Internals of Interrupt Handling:Interrupts and Exceptions Handling] 1. Time, Clocks and Timers |
1. Process Creating, Management and Destroing 1. Process Scheduling 1. Inter Process Communication 1. Memory Addressing 1. Memory Management 1. Reclaiming Pages 1. Process Address Space 1. [:KernelHacking-HOWTO/Subsystems/Exceptions and Interrupts Handling:Exceptions and Interrupts Handling] 1. Deferring Work: Tasklets and SoftIRQ |
Line 7: | Line 15: |
1. Inter Process Communication 1. Memory Management, Virtual Memory Management 1. Virtual File system 1. Process Scheduling |
1. Time Management |
Line 12: | Line 17: |
1. Modules | 1. Virtual File System 1. Accessing Directories and Files 1. Block I/O Layer 1. Page Cache 1. Device Drivers, Kobjects and Sysfs 1. Module Management: Insert Code at Run-Time |
Parent Node : [:KernelHacking-HOWTO:KernelHacking-HOWTO]
The Linux kernel can be thought as logically composed of many Subsystems. They may be not implemented as separate directories in the tree structure due to the tight coupling among them all.
- Process Creating, Management and Destroing
- Process Scheduling
- Inter Process Communication
- Memory Addressing
- Memory Management
- Reclaiming Pages
- Process Address Space
[:KernelHacking-HOWTO/Subsystems/Exceptions and Interrupts Handling:Exceptions and Interrupts Handling]
- Deferring Work: Tasklets and SoftIRQ
- Synchronization
- Time Management
- System Calls
- Virtual File System
- Accessing Directories and Files
- Block I/O Layer
- Page Cache
- Device Drivers, Kobjects and Sysfs
- Module Management: Insert Code at Run-Time
- Add More