Kernel code always executes in one of two contexts:
- Process
- Interrupt
It's easy to get confused here. Remember, this discussion applies to the context in which kernel code executes, not userspace code.
- Title Page
- Copyright and Credits
- Packt Upsell
- Contributors
- Preface
- Linux System Architecture
- Virtual Memory
- Resource Limits
- Dynamic Memory Allocation
- Linux Memory Issues
- Debugging Tools for Memory Issues
- Process Credentials
- The traditional Unix permissions model
- Summary
- Process Capabilities
- Process Execution
- Process Creation
- Signaling - Part I
- Why signals?
- Available signals
- Handling signals
- Using the sigaction system call to trap signals
- Reentrant safety and signalling
- Powerful sigaction flags
- Summary
- Signaling - Part II
- Timers
- Multithreading with Pthreads Part I - Essentials
- Multithreading concepts
- What exactly is a thread?
- Multiprocess versus multithreaded
- Motivation – why threads?
- A brief history of threading
- Thread management – the essential pthread APIs
- Summary
- Multithreading concepts
- Multithreading with Pthreads Part II - Synchronization
- Multithreading with Pthreads Part III
- Thread safety
- Thread cancelation and cleanup
- Threads and signaling
- Threads vs processes – look again
- Pthreads – a few random tips and FAQs
- Summary
- CPU Scheduling on Linux
- Advanced File I/O
- Troubleshooting and Best Practices
- Other Books You May Enjoy
Execution contexts within the kernel
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.