• 0 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: June 7th, 2023

help-circle








  • If you want a good CPU design with a 16-bit address space, take a look at the PDP-11.

    Which was used in home computers, just not in the west

    I agree with you, though. I’m kind of the prime market for this from an educational standpoint. My oldest kid has just learned to read and write (kind of). She’s fascinated by computers. She’s only played retrogames (happily) thus far, so she wouldn’t be put off by the 8-bit era’s graphics or sound.

    But even so…what would I be hoping to teach her with this? How to work around the quirks of the 6502 that are not applicable to literally anything else? That life is full of unnecessary obstacles and frustration? That she could have learned more interesting programming in an easier way if I’d got her a computer with a flat memory model? I’m kind of meh on it.







  • Another Oregan Trail generation here.

    I’m curious about what’s going to happen with Gen Alpha. Any other moms and dads here exposing their kids to retrotech? I have two little ones that I’ve made a DOSBox installation for (Mixed-Up Mother Goose and Donald Duck’s Playground are their favourites). I do wonder how they’re going to think about old tech when they’re older. I haven’t told them that it’s “old” or “retro” yet, so they just think they’re normal fun games.





  • It’s a bit more complicated than that. System load is a count of how many processes are in an R state (either "R"unning or "R"eady). If a process does disk I/O or accesses the network, that is not counted towards load, because as soon as it makes a system call, it’s now in an S (or D) state instead of an R state.

    But disk I/O does affect it, which makes it a bit tricky. You mentioned swapping. Swapping’s partner in crime, memory-mapped files, also contribute. In both of those cases, a process tries to access memory (without making a system call) that the kernel needs to do work to resolve, so the process stays in an R state.

    I can’t think of a common situation where network activity could contribute to load, though. If your swap device is mounted over NFS maybe?

    Anyway, generally load is measuring CPU usage, but if you have high disk usage elsewhere (which is not counted directly) and are under high memory pressure, that can contribute to load. If you’re seeing a high load with low CPU utilization, that’s almost always due to high memory pressure, which can cause both swapping and filesystem cache drops.