c98bdf0019
Gate 0's last structural row. kernel/core/kmem.c: slabs are pages from
kalloc() with a header at the front, and free objects hold the free list in
their own first eight bytes.
That last detail is the whole design. **An object carries no header and
freeing performs no search**: the page base of any object *is* its slab, and
the slab names its cache. It is also exactly why an object cannot exceed a
page, which matters below.
Two interfaces. kmem_cache_create/alloc/free for a subsystem with one kind of
thing -- it gets its own line in /proc/slab, which is most of why naming it is
worth the argument -- and kmalloc/kmfree over power-of-two classes from 16 to
2048 for code with no single type to build a cache around. Each cache keeps
partial and full lists; a slab that empties goes straight back to kalloc()
rather than being kept, so /proc/slab never overstates what is held.
`make kmem-test` asserts the bookkeeping on the build machine. Same arrangement
as schfs-objtest, and for the same reason: slab lists, free-list threading, the
page-to-cache lookup and whether pages actually come back are all things that
can be wrong without a kernel to be wrong in. 26 checks, including one that a
permissive allocator cannot pass -- write a distinct pattern through 512
objects and read them all back, because two objects sharing storage shows up
there and nowhere else.
One bug the test found immediately: kmem_max_obj() returned the raw page
remainder, which kmem_cache_create() then rounded *up* past its own limit. The
largest legal size was reported as illegal.
**It does not do what the register said it would.** The claim was that every
fixed table exists to work around kalloc. Measured:
struct proc 10656 NPROC 128 larger than a page
struct socket 4928 NSOCK 32 larger than a page
struct buf 4272 NBUF 256 larger than a page
struct inode 280 NINODE 200 a cache, bounded on purpose
struct device 120 NDEVICE 32 3.8 KB, never hit
struct file 48 NFILE 512 24 KB, never hit
The three largest cannot go in a page-backed slab whatever it does. NINODE is
a cache and is meant to be bounded. NFILE and NDEVICE are small enough that
their tables are rounding errors and their ceilings have never been reached.
Freeing the big ones needs a contiguous multi-page allocator, which is a
different thing and is not written. That is now in the register and in
docs/architecture/kernel.md rather than left as a claim nobody checked.
What it does fix is real, and was measured rather than assumed:
- **A pipe is 640 bytes and came from a whole 4096-byte page.** Every `|` in
a shell command burned three and a half kilobytes it never touched. Six
pipes per page now, and /proc/slab shows the page going back when they
close.
- **procread() built its answer in a 2048-byte array on the kernel stack**,
under a comment that had warned about exactly that since it was written --
it stayed a local because a whole page for 2 KB felt worse, and kmalloc is
the answer that was missing. Its frame is 64 bytes now instead of ~2100.
- procfs's other generator took a page from kalloc for the same 2 KB.
Verified on a boot: /proc/slab tracks pipe and kmalloc-2048 through real
pipelines, allocs and frees balance, and $(), ps, time, readlink, sigtest and
rename are all still green with no traps.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
56 lines
1.8 KiB
Text
56 lines
1.8 KiB
Text
# Build output. Everything here is reproducible from `make`.
|
|
build/
|
|
schos.img
|
|
schos.iso
|
|
*.o
|
|
*.d
|
|
*.asm
|
|
*.sym
|
|
|
|
# The staged root filesystem. Assembled by the build from cmd/, lib/ and
|
|
# ports/ -- tracking it would mean committing a second copy of every binary
|
|
# on every build.
|
|
sysroot/
|
|
|
|
# Upstream tarballs, fetched not authored: musl, toybox, mksh, dash, the DOOM
|
|
# WADs and usb.ids. 61 MB of other people's release artefacts, all of which
|
|
# the build downloads again if they are missing. The patches that matter are
|
|
# under ports/*/patches/ and those *are* tracked.
|
|
dist/
|
|
|
|
# Test and screenshot output.
|
|
*.log
|
|
*.ppm
|
|
*.png.tmp
|
|
|
|
# Claude Code's per-machine settings (permissions granted on this host).
|
|
# .claude/memory/ IS tracked -- it is the project memory, and committing it is
|
|
# how it survives a directory rename and reaches the other machines.
|
|
.claude/settings.local.json
|
|
|
|
# Emacs lock files: dangling symlinks like .#README -> user@host.pid, left
|
|
# behind when a session ends badly. One was committed in the initial import.
|
|
.#*
|
|
*~
|
|
\#*\#
|
|
|
|
# Build output under projects/ -- these are programs that run on SchOS, and
|
|
# their binaries were tracked by accident.
|
|
projects/schcom/schcom
|
|
projects/schcom/schcom-demo
|
|
|
|
# A built ISO dropped next to the site for download.html. 62 MB; not source.
|
|
docs/Website/releases/
|
|
|
|
# Kernel modules, ever. docs/plan/ldls.md rule 1: LDLS ships the layer and
|
|
# never the thing it loads, and that applies to this tree as well as to an
|
|
# image. The loader's test input is built from ldls/test/refmod.c, which is
|
|
# ours; a .ko here would be someone else's GPL code in an Apache-2.0 repo.
|
|
*.ko
|
|
*.ko.xz
|
|
|
|
# Core dumps from host-side test harnesses (tools/*test.c run on the build
|
|
# machine). One of these got committed once; the pattern is cheaper than
|
|
# remembering.
|
|
core
|
|
core.*
|