no92

If I'm not mistaken, this is just fractal mapping, which is very common. See https://wiki.osdev.org/Fractal_Page_Mapping

Getting OpenJDK ported is quite hard, congrats!

Depending on the jurisdiction, the minimum required storage time for medical data varies - but it needs to be kept around usually. Patients can, within that time frame, request that data to be provided, but may be required to pay some fee to cover the material costs. In my jurisdiction, this time frame is 10 years, and radiology data is usually provided as a paper slip with a link and password, valid for 1-2 years, or DVDs on request.

Keeping that data around and managing requests for it is a part of why older physicians are so keen to sell their practices to younger doctors here - they can pass on the duty of keeping up with storing the data that way.

Not detracting from the point you're making, but the kernel side for Nvidia drivers for Linux is published on GitHub, by Nvidia. The userspace side is still delivered as pre-compiled binaries, tough.

I have managarm installed on a partition on my testing ThinkPad. The steps needed to get it set up were creating the partition, copying over the sysroot, and adding an entry to my grub configuration.

The ARM and RISC-V ports are in different states of being a work-in-progress.

I honestly don't get the leaf blower analogy of the article.

A bit of a side note, but leaf blowers are the stupidest invention I can think of off the top of my head. They are noisy, polluting, inefficient machines that serve no purpose other than to annoy neighbors of lazy people who feel like using a rake is beyond their physical capacity.

tldr pages do exactly this.

https://tldr.sh

I would have never thought to phrase bit-shuffling as deinterleaving, which makes so much more sense to my not-professionally-computer-related eyes and mind.

Realistically though, how likely would a GCC/clang be to emit these instructions when I'm working on some lookup tables, assuming I permit it to use them (e.g. via `-march=native` on a machine that supports the extension)? My gut feeling would be that unless I specifically make sure to structure my code to be as close to the semantics of the instructions as possible, these instructions would never ever be emitted. Or has the world of compiler optimizers advanced enough that rewriting that is commonplace now?

Nice to see managarm mentioned! managarm does have vastly different goals though, as in running Linux software unmodified (i.e. compiled from source, not necessarily binary compatible due to ABI differences) on a fully async microkernel, including desktop apps a user might find useful for general-purpose stuff. Currently, we run weston (the wayland reference compositor) and have support for Xwayland and some graphical applications (as both Qt and GTK are ported). However, there's still a large part of Linux' API surface to be covered, so support will only improve with time.