327 karma · joined November 19, 2017
[1] https://www.phoronix.com/news/Google-User-Thread-Futex-Swap
I wonder how pack compares to it, but its home page and github don't tell much.
A nice blog on this: https://stackedboxes.org/2017/05/01/acklams-normal-quantile-...
But the examples given are... google search results and articles from big publishers, things made to cast a wide net. Those were never good ways to communicate with other people online imo. If you want to interact with real people look for smaller communities and individual creators.
I don't really get this part. The docs for acquire say:
> memory_order_acquire A load operation with this memory order performs the acquire operation on the affected memory location: no reads or writes in the current thread can be reordered before this load. All writes in other threads that release the same atomic variable are visible in the current thread
The prefetch is already ordered before the load in the same thread.
I wouldn't say that tooling is not aware of all that. For example, top and htop display virtual memory and resident memory and shared memory. You need to look at resident memory if you want to know physical memory usage.
There are ways to do this automatically but they're far from perfect. Artists usually take the mesh and literally unwrap it until it's planar, and convert this transformed mesh to the UV mapping. The advantage of this method is that it gives you very good control of seams and texture islands, but it's tricky to preserve surface area.
Those neural rendering methods are very cool because they use light/color fields, but they still have a lot of catching up to do compared to modern 3D graphics.