Interactive Map of Linux Kernel (makelinux.github.io)

I work in Linux kernel related stuff, and from a brief inspection it doesn't seem like the items are terribly inaccurate, but they're not perfect. For example, kmem_cache_alloc() is listed under memory mapping, but it has nothing to do with mapping memory. It's just an API for the slab allocator which is very widespread, and also underpins kmalloc().

The bigger concern is that it doesn't seem like the map is even close to complete. For example, the VFS (virtual file system) is made up of files (open file descriptions), inodes (representing files on disk), and dentries (representing the file system tree/DAG). Probably others things I'm missing too. The area of this page describing vfs only seems to mention files and inodes, and it strangely mentions fsnotify, which is definitely an important subsystem, but not a fundamental data structure like a dentry.

I would imagine people wrote articles about topics, and they got categorized into this very cool visualization. But it's not as if it represents everything, just the things the contributors of the site were working on. It's still very cool, but don't expect that this is a comprehensive overview of the kernel, or that all the major parts of a particular area are listed here.

Edit: but that said, resources from 2010 or earlier can be quite useful. I have a cherished hard copy of Understanding the Linux Virtual Memory Manager[1] which was released in 2007 about Linux 2.4, and I regularly rely on it and its concepts. I have another beloved copy of Linux Kernel Development 3rd Ed. (2010) [2] which is how I learned a ton of fundamentals. Ultimately, it's not about the age of the resource but the concepts behind it :)

[1]: https://www.kernel.org/doc/gorman/pdf/understand.pdf [2]: https://altair.pw/pub/doc/unix/Linux%20Kernel%20Development%...

Seems to have been kept fairly updated

https://github.com/makelinux/linux_kernel_map

https://github.com/makelinux/makelinux.github.io

Looks like a big SVG made with Inkscape:

    xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"

And the controls seem to be made with https://github.com/timmywil/panzoom:

    <script src="https://unpkg.com/@panzoom/panzoom@4.5.1/dist/panzoom.min.js"></script>
    <script type="text/javascript">
        const panzoom = Panzoom(elem, {
            maxScale: 12
        })

        m = {
            animate: true,
            relative: true,
            maxScale: 80
        }
        right.addEventListener('click', function() {
            panzoom.pan(100, 0, m);
        })
        left.addEventListener('click', function() {
            panzoom.pan(-100, 0, m);
        })
        lu.addEventListener('click', function() {
            panzoom.pan(-100, -100, m);
        })
        up.addEventListener('click', function() {
            panzoom.pan(0, -100, m);
        })
        ru.addEventListener('click', function() {
            panzoom.pan(100, -100, m);
        })
        down.addEventListener('click', function() {
            panzoom.pan(0, 100, m);
        })
        ld.addEventListener('click', function() {
            panzoom.pan(-100, 100, m);
        })
        rd.addEventListener('click', function() {
            panzoom.pan(100, 100, m);
        })
        center.addEventListener('click', panzoom.reset)
        zoom_in.addEventListener('click', panzoom.zoomIn)
        zoom_out.addEventListener('click', panzoom.zoomOut)
        elem.parentElement.addEventListener('wheel', panzoom.zoomWithWheel)
    </script>

It's a driver intended for use by userspace, not part of the core kernel, so it'd be a better fit on a map of Android subsystems

Install fsn on Linux, navigate to /usr/src/linux .. have fun!

I didn't get the reference, so I looked it up: https://en.wikipedia.org/wiki/Fsn_(file_manager)

We’re one step closer to hacking the Gibson

https://youtu.be/b2OYNMO_mNw?si=Mg1XISFnF2DNS-ZU

not on firefox + win10

Not sure if I fully understand what you mean, but...

If you hold down the <ctrl> key while you use the mouse to drag/pan/etc, it stays on the page while links open.