Linux 2.4 VM Documentation 115
popoutman writes "Mel Gorman has announced the availability of a guide to the 2.4 kernel VM
including a walkthrough of the VM code. Anyone interested in obtaining a solid understanding of the Linux 2.4 VM will certainly want to take a look at this documentation. Mel says that the effort is at least several weeks from being finished, but that he's releasing it now with the hopes of getting feedback to be sure he's on the right track.
He also notes that the 2.5 VM is still too much of a moving target for him to document it just yet." See also a Kerneltrap story.
Where I work (Score:5, Funny)
Well maybe not all the time and with serveral itterations, but I only manage your credit raiting, not you kernel VM.
Re:Here's a tip for the author. (Score:1, Funny)
VM = Value Management
VM = Variable Metric
VM = Velocity Management
VM = Velocity Meter
VM = Velocity Modulation
VM = Version Manager
VM = VIBE Magazine
VM = Video Monitor
VM = Vietnam (Socialist Republic of Vietnam)
VM = View Mail (Emacs)
VM = Virtual Machine
VM = Virtual Madness
VM = Virtual Memory
VM = Vivamos Mejor (Let Us Live Better; Guatemalan agency)
VM = Voice Mail
VM = Voice Message
VM = Voice Modulation
VM = Voltmeter
but not that one!!!
every developer worth his salt knows... (Score:5, Funny)
Re:This should be helpful (Score:5, Funny)
Define your function "Olog", please. Surely Mr. "Wagner LLC Consulting Co. - Getting it right the first time" couldn't have meant O(log n)... :)
Re:JVM (Score:5, Funny)
Re:every developer worth his salt knows... (Score:2, Funny)
Re:JVM (Score:5, Funny)
There used to be a kernel-space HTTP server. It was integrated into the kernel for a specific reason: zero-copy access to the network interface memory. It was fast and relatively feature-poor. If it crashed (fortunately, a rare occurance), you got a kernel panic.
Along came a user-space, zero-copy HTTP server. It was faster and had a few more features to boot. Being a user-space program, if it crashed, you got a core-dump. It could also be run in a chroot jail, a gigantic step more secure than running in ring-0.
Two lessons can be read from this:
1. Don't integrate something with the kernel unless there is a specific advantage you hope to gain from it. Will making a JVM part of the kernel really speed it up? Are you sure?
2. Don't under-estimate the speed of a properly designed user-space Linux program. The kernel developers have done a magnificant job tuning the kernel and providing APIs for performance-critical apps.
Re:JVM (Score:4, Funny)
copulating modules (Score:2, Funny)
Generally, related operations are clustered together in the same file and there is not much copulation between modules.
I hope the discovery channel will do a special on copulating modules some day. I've seen module coupling but no copulation yet.
Re:copulating modules (Score:2, Funny)
> modules some day. I've seen module coupling but no copulation yet
Haven't you ever heard of sexy code? Is is meant to be taken literally, isn't it?
(typo corrected in the work in progress version)