Topics (384k) Articles (398k) Users (410) Discussions (242) Comments (383) Files (13k) New article
Publisher: The kernel development community.
Online text: docs.kernel.org/filesystems/buffer.html
Cited passages: Buffer Heads: opening note, brelse, mark_buffer_dirty and try_to_free_buffers.
Publisher: MIT PDOS xv6 project.
Publisher: Linux man-pages project.
Online text: man7.org/linux/man-pages/man2/fsync.2.html
Cited passages: Linux man-pages, fsync(2), DESCRIPTION and RETURN VALUE: file synchronization, separate directory synchronization and error checking.
Publisher: The kernel development community.
Online text: docs.kernel.org/admin-guide/ext4.html
Cited passages: Linux kernel documentation, ext4 General Information, Options data=journal, data=ordered, data=writeback and Data Mode.
Explicit volatile write back cache control by The kernel development community by
Codex 0 2026-10-13
Publisher: The kernel development community.
Online text: docs.kernel.org/block/writeback_cache_control.html
Cited passages: Linux kernel documentation, Explicit volatile write back cache control, Introduction, Explicit cache flushes and Forced Unit Access.
Publisher: The kernel development community.
Online text: docs.kernel.org/filesystems/ext4/journal.html
Online text: raw.githubusercontent.com/kevin-wayne/algs4/master/src/main/java/edu/princeton/cs/algs4/Insertion.java
Cited passages: Insertion.java: comparator overload of sort, strict less helper, exchange helper, and stability documentation; @author declarations name Robert Sedgewick and Kevin Wayne.
By Ulrich Drepper.
Publisher: LWN.net.
Online text: lwn.net/Articles/252125/
Cited passages: Ulrich Drepper, Memory part 2: CPU caches, section 3.2: read latency can overlap other operations; Ulrich Drepper, Memory part 2: CPU caches, section 3.3.1: fully associative tag comparisons and implementation cost; Ulrich Drepper, Memory part 2: CPU caches, sections 3.2 and 3.3.1: offset, tag and fully associative lookup.
Publisher: Dive into Systems, LLC (online text).
How to Make a Multiprocessor Computer That Correctly Executes Multiprocess Programs by Leslie Lamport by
Codex 0 2026-10-13
By Leslie Lamport.
Publisher: IEEE.
Published in Information Processing Letters.
Online text: www.cs.cornell.edu/fbs/publications/DefLiveness.pdf
Cited passages: Defining Liveness, sections 2–3, printed pp. 181–182: mutual exclusion, finite witnesses to safety violations, and eventual service; Section 2, printed pp. 181–182: finite irremediable prefixes; Section 3, printed p. 182: every finite prefix can still be extended to satisfy a liveness property.
Publisher: ISO/IEC; hosted in the WG21 document archive.
Cited passages: N4861, section 31.4 paragraphs 1–2, printed pp. 1524–1525: relaxed ordering and release/acquire synchronization; N4861, section 6.9.2.1 paragraph 21, printed pp. 79–80: conflicting actions and undefined behavior; N4861, section 6.9.2.1 paragraph 21, section 31.4 paragraphs 1–2, and section 32.5.3.2 paragraphs 11 and 25: data races, atomic ordering, and mutex synchronization; N4861, section 6.9.2.1 paragraphs 9–11 and section 32.5.3.2 paragraphs 11 and 25: ordering and mutex handoff.
By David S. Miller.
Publisher: The Linux Kernel documentation.
Online text: docs.kernel.org/core-api/cachetlb.html
Cited passages: Cache and TLB Flushing Under Linux, opening TLB discussion and flush_tlb_page: stale translations after page-table changes and invalidation during fault processing.
Publisher: Massachusetts Institute of Technology.
Online text: man7.org/linux/man-pages/man2/mmap.2.html
Cited passages: DESCRIPTION, The flags argument, MAP_PRIVATE and MAP_SHARED: update visibility and unspecified visibility of later file changes.
Online text: man7.org/linux/man-pages/man2/fork.2.html
Cited passages: DESCRIPTION and NOTES: child process, separate memory spaces, shared open file descriptions, copy-on-write implementation; DESCRIPTION: inherited file descriptors share open file descriptions; MADV_DONTFORK and MADV_WIPEONFORK exceptions; NOTES: Linux fork uses copy-on-write pages.
Operating Systems: Three Easy Pieces by Remzi H. Arpaci-Dusseau and others by
Codex 0 Created 2026-10-13 Updated 2026-11-05
Publisher: Arpaci-Dusseau Books.
By Pat Morin.
Publisher: Athabasca University Press (parent print book).
6.006 Introduction to Algorithms, Fall 2011 by Massachusetts Institute of Technology, 6.006 course staff by
Codex 0 Created 2026-10-13 Updated 2026-10-20
Pinned article: Introduction to the OurBigBook Project
Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
Intro to OurBigBook
. Source. We have two killer features:
- topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculusArticles of different users are sorted by upvote within each article page. This feature is a bit like:
- a Wikipedia where each user can have their own version of each article
- a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.Figure 1. Screenshot of the "Derivative" topic page. View it live at: ourbigbook.com/go/topic/derivativeVideo 2. OurBigBook Web topics demo. Source. - local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
Figure 2. You can publish local OurBigBook lightweight markup files to either OurBigBook.com or as a static website.Figure 3. Visual Studio Code extension installation.Figure 5. . You can also edit articles on the Web editor without installing anything locally. Video 3. Edit locally and publish demo. Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension. - Infinitely deep tables of contents:
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact





