GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • The Linux Kernel
  • Development process
  • Submitting patches
  • Code of conduct
  • Maintainer handbook
  • All development-process docs
  • Core API
  • Driver APIs
  • Subsystems
  • Locking
  • Licensing rules
  • Writing documentation
  • Development tools
  • Testing guide

This view

  • Original page
  • New address

GeezerVison is showing www.kernel.org — Kernel Hacking Guides — The Linux Kernel documentation

English
  • Chinese (Simplified)
  • Italian

Kernel Hacking Guides¶

  • Unreliable Guide To Hacking The Linux Kernel
    • Introduction
    • The Players
    • Some Basic Rules
    • ioctls: Not writing a new system call
    • Recipes for Deadlock
    • Common Routines
    • Wait Queues include/linux/wait.h
    • Atomic Operations
    • Symbols
    • Routines and Conventions
    • Putting Your Stuff in the Kernel
    • Kernel Cantrips
    • Thanks
  • Unreliable Guide To Locking
    • Introduction
    • The Problem With Concurrency
    • Locking in the Linux Kernel
    • Hard IRQ Context
    • Cheat Sheet For Locking
    • The trylock Functions
    • Common Examples
    • Common Problems
    • Locking Speed
    • What Functions Are Safe To Call From Interrupts?
    • Mutex API reference
    • Futex API reference
    • Further reading
    • Thanks
    • Glossary
  • False Sharing
    • What is False Sharing
    • False Sharing Pitfalls
    • How to detect and analyze False Sharing
    • Possible Mitigations
    • Miscellaneous
©The kernel development community. | Powered by Sphinx 5.3.0 & Alabaster 0.7.16 | Page source
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.