Swap is rarely hit, especially if set up with zram.

This is not a good thing btw. Any unused anonymous page takes up space that could instead be used for file-backed pages that make your system faster.

Multiple swap tiers beyond zram/zswap

Swap is not tiered storage!

Priorities control order of preference, not tiers. If you run out of space on a higher priority, it will not move that swap's data to a lower priority swap. It will keep all of it exactly where it is and new data will hit the lower prio swap instead, no matter how hot it is.

Intel Optane

Cool tech but it's dead and was quite niche even when it was alive.

zram write-back device

Not a thing you actually want to use for swap. It's not an automatic writeback that is integrated into the Linux MM in any way. (Probably has some use-case for non-swap zram purposes though.)

Large HDD swap partition used as a third tier swap disk

This makes no sense at all unless you are extremely space-constrained on the NVMe and absolutely must not OOM – even if progress stalls to an absolute crawl.

swapped pages can be moved around by the user (or a tool), by turning swap devices off and on.

This is neither feasible nor desirable. You don't have enough granularity to do anything useful by doing so.
Even if you had, it'd work against the MM because it resurrects pages as "hot" that have been cold for a long time.
In any situation where swap is important, making the kernel think cold pages are hot is the very last thing you want.

---

I too wish it were but tiered/transcedental memory is not a thing in Linux and these hacks do not change that fact; they merely look similar if you don't look close enough.

I cannot think of a single use-case where this would be preferable to a decently sized physical swap with zswap XOR just zram swap (if physical swap is infeasible).

This testing compares apples to oranges. Differently sized swap and quite obviously different workloads. Given how very much compress ratios depend on the specific data that is compressed, this experimental setup cannot produce valid results.

This is exacerbated by your swap being full. Zswap is more of a cache in front of your actual swap; it requires physical swap to function. If the physical swap is full, it cannot receive more data! Zswap not doing very much when the swap is full is totally expected behaviour because it simply doesn't. The solution to that is to size your swap sensibly. (Admittedly, this does not appear to be documented clearly.)

zswap uses the exact same allocator as zram these days (zsmalloc). It'd be very surprising if it had different space efficiency characteristics. It's not impossible (could be a bug) but claiming so would require quite certain evidence IMHO.

RE: LRU inversion: the problem with not caring about it is that it's not a visible problem until it very suddenly is. Your system will not gradually degrade but very suddenly and unpredictably hit a wall that it cannot get itself over.

I fact-checked and it's true; what the hell are they smoking‽ o.O

I was planning on getting one some day as it ticks all the boxes but this is just.. embarrassing.

There's https://gitlab.com/android_translation_layer/android_translation_layerwhich can already run BeatSaber apparently.

I think games specifically might be easier than most other apps as they are probably often little more than a 2D canvas displaying a regular Linux app with quite limited use of android-specific APIs.

Inconsistent time before sleep is likely the kernel waiting for IO to sync to disk.

Not going to sleep at all implies a serious issue that prevented the kernel from doing so. Check your logs!

Suspend reliability greatly depends on the firmware of your specific device as it controls the wakeup.

On my Framework 16 for instance, it is very reliable these days. I can't remember the last time it woke up unexpectedly and I'm not sure whether it happened even once since the firmware update that fixed a major oversight in keyboard wakeup (waking when a key was pressed through a closed lid).

In Hyprland, how it works is that you define the screen lock command (e.g. swaylock) in hypridle and that gets wired into logind somehow such that you can loginctl lock-session.

I then (also in hypridle) define a before sleep hook that locks the session.

I believe the proper way to do this would be to run your lockscreen as a systemd unit that is WantedBy and Before suspend.target. This would in theory take care of making it idempotent and reliably show the lockscreen before initiating suspend.
A friend of mine has this sort of setup and, while it is reliable, the lockscreen is still racy and sometimes only triggers after suspend. Might be the lockscreen unit not signalling its readiness to systemd properly though.

Well, they have – I think. When you download an edited image, it supposedly downloads an image with edits applied. The original is optionally available too.

If you download the edited image, this is effectively equivalent to the status quo of image editing.

PM is automayically E2EE too if the recepient's server supports WKD or has uploaded their pubkey to keys.openpgp.org.

Thank you!

I've found the Seedstudio thing after posting this too and it looks like the thing I'd be looking for!

What's your experience w.r.t. coverage?
Obviously that highly depends on where exactly you are – you certainly aren't going to have coverage in the outback – but I'm mostly concerned with places where people actually go and would take my bag/laptop/bicycle to. 'Stralia is going to generally be quite different from Germany too of course but it would be a good reference point from which I could extrapolate.

The issue is not the instruction set of the processors. That's actually quite well standardised with ARM (albeit unfree) and there is plenty of generic support for it because of that.

The issue is all the "peripheral" devices such as WiFi, WWAN, display etc. that are wired up in extremely bespoke device-specific ways. They are usually implemented in vendor kernels with millions of lines of divergence to mainline at best and/or proprietary blobs at worst.

Changing the ISA from one well-supported closed standard to a less well-supported open one will not change that issue one bit.