Linux Kernel Design Patterns - Part 1
Jun 19, 2009, 13:33 (1 Talkback[s])
(Other stories by Neil Brown)
No-Size-Fits-All! An Application-Down Approach for Your Cloud Transformation REGISTER >
"One broad approach that has found some real success is to
increase the visibility of various aspects of the kernel. This
makes the quality of those aspects more apparent, so this tends to
lead to an improvement of the quality.
"This increase in visibility takes many forms:
* The checkpatch.pl script highlights many deviations from
accepted code formatting style. This encourages people (who
remember to use the script) to fix those style errors. So, by
increasing the visibility of the style guide, we increase the
uniformity of appearance and so, to some extent, the quality.
* The "lockdep" system (when enabled) dynamically measures
dependencies between locks (and related states such as whether
interrupts are enabled). It then reports anything that looks odd.
These oddities will not always mean a deadlock or similar problem
is possible, but in many cases they do, and the deadlock
possibility can be removed. So by increasing the visibility of the
lock dependency graph, quality can be increased."
- Drizzle: Rethinking the MySQL Database Kernel(Jun 16, 2009)
- Testing Out The SSD Mode In Btrfs(May 29, 2009)
- Big Mess o' Wires Homemade CPU(May 29, 2009)
- Linux 2.6.30 Kernel Benchmarks(May 29, 2009)
- GNU ARM toolchain embedded development on Linux(May 21, 2009)
- Detecting memory leaks & invalid memory de-allocation in the Linux kernel(May 18, 2009)
- Kernel Log: What's coming in 2.6.30 - Storage: RAID improvements, optimised CFQ Scheduler(May 17, 2009)
- Linux SOHO NAS offers iSCSI(May 06, 2009)
- File Systems, Disk Defragmentation and more.(Apr 27, 2009)
- Reverting to older kernel under Ubuntu(Apr 23, 2009)
- Open Source SSL Acceleration(Apr 16, 2009)