A technical joke thread on X satirizes low-level computer architecture concepts including virtual memory, TLBs, and branch predictors

@__femb0t Not just to trick processes into thinking they have contiguous addresses, also so that those contiguous addresses can be served by a fragmented physical memory

@__femb0t Why don't you properly quote the tweet? Why an image?

@__femb0t That’s my Mutual ! @tomieinlove is an amazing poaster you should 💯 follow

@__femb0t They were right, Specter and Meltdown came from our hubris 😞

@__femb0t vmmap was a mistake and I’ll die on that hill

@__femb0t

@__femb0t (MP): would not yon TLB become fettered with the vast multitudes of 4kb pages?

(Me): yes, so we dynamically adjust the size of pages into megabytes, "Virtual Huge Pages."

(MP): ah, so even the digital landowners have The Lord's Acre ...

@__femb0t Thank you

@__femb0t u should follow tomieinlove

@__femb0t This is just every time Carter talks to an off-worlder.

@__femb0t source:

@midnucas @__femb0t And for paging to disk!

@__femb0t @xai should detect this and replace the tweet image with the actual tweet automatically. Hire me and I will build that feature for you. 😇

@__femb0t Real

@WixWoz @__femb0t each process is granted a specific memory region owned by its parent process to directly manipulate io

@WixWoz @__femb0t I am glad you asked!

I am currently researching the notion of replacing it with a dma capability based memory reference map that allows for inescapable memory constrained address space for directed io

@AlexCaswen @__femb0t tyyyyyyy

@__femb0t Speculative execution is orthogonal in purpose and mechanism from caches

@__femb0t Tomie and himbo are both clutch

@WixWoz @__femb0t it’s a memory reference that is zero-copied to an actual memory region somewhat like a hierarchical capability grant upwards through privileged delegation eg

process > parent(n) > “driver”