They did mention they saw 4GiB of eviction for a single 32MiB scan out image.

So while I would call the image allocation small, it seems to cause an avalanche of evictions. Amplified by the fact that each frame has one of these images, though I expect subsequent frames might have a better chance of already fitting into evicted space.

What I don't exactly understand is: doesn't it make sense to always reserve the contiguous physical memory for this case and not allow anything else to be put in it?

Maybe we can get a few MI350P's out of that then :) Surely it will be easy to do :clueless:

On a more serious note, I do wonder if it would theoretically be possible to put HBM on something like CAMM instead of regular DDR? I have not done any research on this.

I always crave milk. That is why I always have milk on hand and if I for some reason need more milk one day I get more milk than usual, but I will still always have at least a little bit of milk on hand.

While I get where you are coming from, but the government isn't just a static thing that once you've done something it will stay like that. New procedures and jobs come and go all the time and will always need some form of optimisation.

I dunno if its just me, but having a manual override for such important/basic stuff is kind of a must for me. As much as I enjoy smart home stuff, having anything critical only available via that is just stupid.

[0]: https://www.reddit.com/r/LocalLLaMA/comments/1vef79c/quantiz...

> Really it should probably be part of SystemD

https://github.com/systemd/systemd/pull/39855

I am unsure what you you mean with this? If you are talking about choosing a different browser on mobile I will point you to the DMA Browser Choice Screen page for Android[1], it has been a thing for a while as far as I can remember.

[1]: https://www.android.com/choicescreen/dma/browser/

I dunno, "things not working the way I expect" is very subjective.

I personally think it makes more sense that processes do not outlive the parent from which they come (in this case processes spawned from a user shouldn't outlive that user) unless you explicitly go through something which outlive the parent (process manager in this case (e.g. running via systemd-run)).

Though I am also strongly of the opinion of just because something is a feature, does not mean it is good to keep around, e.g SUID/SGID (which has a similar "I get more than the parent" problem).

Though I guess different people can have different opinions/values on this.

They could, but since its literally just a PC it would just be subsidising PCs for something they likely aren't gonna make their money back, unlike XBOX or PlayStation, which are locked down and you are forced to use their store where they make the money back.

Will they make some of the subsidisation back? Sure, there will be some gamers that will be able to buy it just from pure numbers, but I feel like a massive chunk would just end up as office PCs with Windows on them in some office if subsidised.

The deck might make more sense to subsidise, but to do it for the gabecube doesn't make sense in the world we live in.

It would be a bit more general, for general cooking and be called Cookstral

> Rabbit hole, I know, but so fascinating if you solved it all :)

Encrypting `/boot/` is the wrong thing to do. One can just replace it with something that logs the encryption key instead (and sends it off to somewhere). You actually need to verify that what you expect to be there is actually there and a encryption isn't gonna do that for you.

A reasonably secure boot chain looks roughly as follows: bootloader is checked by the UEFI (read secure-boot), bootloader chain loads a signed UKI which also uses secure boot verification (or just skip the bootloader if you only have a single kernel with no fallback), this then loads a signed dm-verity `/usr/` which brings you to the login screen. Root is just data (e.g. mounted `noexec`) and is encrypted using e.g. PCR 11 so that it only unlocks if the UKI is the one that is expected (with some other backup unlock method).

This is basically #2 of the "Design Goals" of Poetterings "Fitting everything together"[0]. It's a good read if you are looking to designing your own Linux image and are looking for some inspiration. There is ParticleOS[1] which somewhat dogfoods this kind of system, though I don't think it is anything remotely considered for a production system.

[0]: https://0pointer.net/blog/fitting-everything-together.html

[1]: https://github.com/systemd/particleos

If you didn't transfer it from your Mojang account to your Microsoft account in time (before the account was shut down) you just straight up lost access to it.