LibVF.IO VS linux

Maybe you can try LibVF.IO

I'm on Linux and I'm running a 3070 Ti (Nvidia). I have always wanted to do GPU virtualization but because NVIDIA won't release vGPU for consumer card no one can do it without crossing legal red tape or problems with bricking your GPU. I did find this [https://github.com/jamesstringerparsec/Easy-GPU-PV] however it is only for windows, I found this [https://github.com/Arc-Compute/LibVF.IO/] and does not work with my GPU, and this [https://github.com/DualCoder/vgpu_unlock] and can't get it to work. Done any one know an alternative on Linux that work just like this, overcoming these problems (on KVM)?

If you are willing to thinker with you gpu driver you could look up libvfio and create multiple VM with the same gpu.

It seems they have issues with recent drivers/kernel, too: https://github.com/Arc-Compute/LibVF.IO/issues/61

I ran it like a year ago it was fine but not for my workflow. Might revisit the setup soon since it matured a lot since then. I suggest you also look at: https://github.com/Arc-Compute/LibVF.IO

For Affinity, I don't know. I have heard of people using Photoshop via VM, the problem usually comes when you need to utilize a lot of GPU because outside of GPU passthrough (might worth researching single-GPU passthrough and libvfio if you don't want to use two GPUs), GPU performance isn't great for VMs. I did find a few threads on the subject of Affinity on Linux, though, so maybe those could help.

I feel you on this. Looking forward to running libvf. Wine has come a long ways, but I ended up keeping a old PC a secondary to not deal with the hacking/workarounds to run some games. Using the older system for my Linux.

It's theoretically possible using a method like libvfio. This should allow you to split your gpu into 2 virtual gpus. It's designed for use with a vm, but could likely work with multi seat

Perhaps not the "best" source code I've ever read, but libVF.io had some beautiful code for what's generally gnarly system-glue code. The iommu setup code is a good example and inspires me to think that system-glue code doesn't need to be gross or impenetrable: https://github.com/Arc-Compute/LibVF.IO/blob/master/src/libv...

Another one I've appreciated reading (and learned more about 2d graphics from) is Pixie, a 2d graphics library written in Nim. Here's the implementation of a fair subset of SVG paths: https://github.com/treeform/pixie/blob/master/src/pixie/path...

And one last one for basic algorithms: https://github.com/nim-lang/Nim/blob/version-1-6/lib/pure/al...

Of course Knuth's original code is still some of the best classic code. K&R's original C book is a classic.

FFS predates FreeBSD and is in some capacity supported by all 3 major BSDs. I'm fairly confident that Linux actually supports it through the ufs driver ( https://github.com/torvalds/linux/tree/master/fs/ufs ); whether the use of different names in different places makes it better or worse is an exercise for the reader.

These are a bit easier to see what's going on:

https://github.com/torvalds/linux/commit/d5cf50dafc9dd5faa1e...

https://github.com/torvalds/linux/blob/d5cf50dafc9dd5faa1e61...

Unfortunately Github doesn't have a way to render symbols for whitespace, but you can tell by selecting the spaces that the previous version had leading tabs. Linus changed it so that the tokens `default` and the number e.g. `12` are also separated by a tab. This is tricky, because the token "default" is seven characters, it will always give this added tab a width of 1 char which makes it always layout the same as if it were a space no matter if you use tab widths of 1, 2, 4, or 8.

There was also a Gentoo effort to run atop FreeBSD[0]. The challenge of course is that afaik none of the BSD kernel ABIs are considered stable. The stable interface is the BSD libc. That said, with binfmt_misc, I don't see a reason you couldn't just run (at least some) FreeBSD binaries on Linux with a thin syscall translation layer (rather something like qemu-system) and then your layer hooked via binfmt_misc. I'm not aware of anyone who has done this for FreeBSD, but prior efforts existed as alternate binfmts for SysVr4/5 ELF binaries[2]. Either way would take some elbow grease, but you *might* even be able just reuse binfmt_elf and just have a new interpreter for FreeBSD elf.

[0] https://wiki.gentoo.org/wiki/Gentoo_FreeBSD

[1] https://docs.kernel.org/admin-guide/binfmt-misc.html

[2] https://github.com/torvalds/linux/blob/master/fs/binfmt_elf....

> The original less-than check was deemed incorrect

It was only deemed incorrect because of an information leak. Not because it's a valid use-case for user space to copy smaller portions of *hwrpb into user space. https://github.com/torvalds/linux/commit/21c5977a836e399fc71...

Correct. And the combined work needs to carry the MIT license text and copyright attributions for the MIT software authors. With binary distribution it must also be overt, not hidden in some source code drop, but directly accompanying the binary.

Many people who talk about relicensing never credit the MIT developers or distribute the MIT license text. "Because it's GPL now."

I don't think that you believe that, but many developers do.

Some don't see the need for source code scans for Open Source compliance, because the license.txt says GPL, so it's GPL. Prime example is the Linux kernel. There is code under different licenses in there, but people don't even read https://github.com/torvalds/linux/blob/master/COPYING till the end ("In addition, other licenses may also apply.") and conclude it's simply GPL 2 and nothing else.

Also be aware that sublicensing is not the same as relicensing.

> Does he have something against it?

He notoriously hates GNU Emacs, yes.

https://marc.info/?m=122955159617722

https://github.com/torvalds/linux/blob/master/Documentation/...

So If we would only count code and not comments, it is only 9489 LoC Rust. Which would be about 0.03% and if we take all lines and not only LoC it would be around 0.05%

[0] https://github.com/XAMPPRocky/tokei

[1] https://github.com/torvalds/linux/commit/b401b621758e46812da...

AIUI fsync is built on futex_waitv which has been upstreamed. So this has to be more than that.

https://github.com/torvalds/linux/commit/a0eb2da92b715d0c97b...