.NET Runtime VS vgpu_unlock

This issue is still open: https://github.com/dotnet/runtime/issues/35995

Also, it seems that initial memory settings have a big effect on mobile, this is a fix that will make it for 7.0.4 (April): https://github.com/dotnet/runtime/pull/80849

looked it up and engine.cpp seems to only be 8.5k lines, which doesn't seem super unreasonable to work with. It ain't no gc.cpp that's for sure.

Threading.Channel has more or less replaced all the concurrent queue alternatives for me. channels have the benefit of nonblocking wait for when the channel can be written.

My teammate created an issue on GitHub: the developers fixed the order of arguments and added a test.

i have tried with an adapted .editorconfig but even using the "official" dotnet team editorconfig

Technically Mono supports RISC-V, so you can get .NET code running on it. Also it looks like if you're willing to go through messy and poorly documented build processes you can build CoreCLR on RISC-V: https://github.com/dotnet/runtime/issues/36748

So proper support is likely coming soonish, I'd guess by the time .NET 8 comes out.

There's an issue on simplifying WebSockets specifically https://github.com/dotnet/runtime/issues/77060 that may be of interest.

See CLR is also using left/right for its not-quite-binary-tree in SortedSet. Though this also uses the Enum-As-Discriminator trick instead of boolean/array. I know the JVM also has/uses left/right but I can't find the backing source file right now.

Pci passthrough https://github.com/mbilker/vgpu_unlock-rs https://github.com/DualCoder/vgpu_unlock https://github.com/DualCoder/vgpu_unlock/issues/91 https://gitlab.com/polloloco/vgpu-proxmox https://github.com/joeknock90/Single-GPU-Passthrough https://gitlab.com/YuriAlek/vfio#start-here https://www.reddit.com/r/homelab/comments/b5xpua/the_ultimate_beginners_guide_to_gpu_passthrough/ https://forum.level1techs.com/t/single-gpu-passthrough-with-proxmox/113282/2 https://forum.proxmox.com/threads/problem-with-gpu-passthrough.55918/

If you have a spare GTX/RTX lying around you can also simply use https://github.com/DualCoder/vgpu_unlock

OP, this is your only option because the tool vgpu_unlock that would let you split up your card into multiple devices for passthrough on Linux hosts doesn't support Ampere cards like the RTX 3070 yet.

In the meantime I found the spoofing project for Linux, in case you're interested: github.com/DualCoder/vgpu_unlock

The vGPU feature can be unlocked for several Nvidia GPUs: https://github.com/DualCoder/vgpu_unlock

I did not yet try it myself (maybe it doesn't even work anymore?), and it might not be an option for businesses.

Now get vgpu_unlock: cd git clone https://github.com/DualCoder/vgpu_unlock chmod -R +x vgpu_unlock

Another option is to check out the vgpu unlock project. It allows the resources of a GPU to be split between host and VM. However, it only works on newer Nvidia GPUs. (You can look up valid hardware IDs in the project's python script and a site like this.) There has been some discussion about vgpu here, but I've never done it myself.