You should read the whole article, because TMO does differ from traditional swapping. Notably, swapping usually occurs during periods of extreme memory pressure, where as TMO will offload memory much sooner and more intelligently.

So… paging then? Slightly improved paging?

If only there was some way to know! Some kind of... hyperlink, with text, where the answers you seek were available in a language you know, English, perhaps?

The linked article practically goes out of its way to obscure how much this work is incrementally building on Linux’s existing paging design versus designing their own solution. Sure there’s a couple places that mention Linux defaults don’t work for them, but it isn’t all that clear how difficult it was to change things

Thanks for stating my opinion with such clarity. :)

Why come up with these weird acronyms and try to sell it like it’s some entirely new idea? Why not just start that page with “We improved the virtual memory subsystem of the Linux kernel...” and take it from there? That would be both comprehensible and impressive.

Everybody wants to come up with their own terminology from scratch nowadays, even for things that already have well established terminology. For those of us who understand a lot and want to systematize knowledge in our heads it’s such a drag.

Only one way to know for sure!

Nope.

Paging algorithms have been "pre-swapping" for ages in order to keep the free page reserve high (or preferably a purgeable page reserve).

So they found out vm.swappiness?

Ahhh, but they compress the memory!

Anyone else remember Ram Doubler for pre OSX Macs?

Oh yes. Mac OS X started doing that in Mavericks as well

Darwin does it, NT does it, and Linux can do it (I use swap on zram, there's also zswap). Nice to see it widely (if quietly) used:)

IBM once had a main-memory interface that did LZW compression (so compressing between L2 and main memory).