Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)V

vividspecter

@ vividspecter @aussie.zone

Posts
8
Comments
193
Joined
1 yr. ago

  • ollama 0.11.9 Introducing A Nice CPU/GPU Performance Optimization

    Jump

  • Ollama uses ROCm whereas llama.cpp uses Vulkan compute. Which one will perform better depends on many factors, but Vulkan compute should be easier to setup.

  • Blocking tariffs would be "end of the United States," top Trump adviser says

    Jump

  • Not only do they not care, inflicting harm is the entire point for these people.

  • FFmpeg 8.0 “Huffman” Released with AV1 Vulkan Encoder, VVC VA-API Decoding

    Jump

  • SVT-AV1 has also had some pretty major improvements in recent months and years. It's possible if tested even a year ago it will be significantly faster for the same quality today.

  • DeepSeek dropped the V3.1 Weight

    Jump

  • Thanks for the correction. The latter meaning did gain more prominence in recent years in my perception, but it's not surprising that it already existed in the past.

  • DeepSeek dropped the V3.1 Weight

    Jump

  • More like in the past 10 years or so, but yes. On a side note, "leaked" has also subtly changed meaning from the actual product (such as a game being released early through piracy etc) to just information about the product.

  • SR-IOV Will Only Be Supported On Intel Arc Pro Graphics Cards

    Jump

  • They seem to all be committed to limiting this feature to the pro market, which is a shame. At least AMD and Intel have native context support, although it's very early days and Linux host and guests only for now.

  • is Lemmy the most popular 'Reddit Alternative'?

    Jump

  • 404media is exactly the site I would expect to be aware of Lemmy among the semi-mainstream tech outlets (along with TheVerge to a lesser extent).

  • What's one thing your learned at college/university that blew your mind?

    Jump

  • I know people's experience varies on this but I absolutely hated high school, and only discovered that I enjoyed learning as a process because of uni. And I'd probably still be small minded and somewhat bigoted if I hadn't gone. Simply because it forced me to critically evaluate my own views and also exposed me to a number of types of people I wouldn't have encountered otherwise.

    It's a shame it's so expensive in some countries, because I think it's important to have a well-educated society more broadly.

  • Duckstation(one of the most popular PS1 Emulators) dev plans on eventually dropping Linux support due to Linux users, especially Arch Linux users.

    Jump

  • I suggest using Beetle mednafen, unless you're on a very slow system. Or Swanstation, it's not like that's going away.

  • Duckstation(one of the most popular PS1 Emulators) dev plans on eventually dropping Linux support due to Linux users, especially Arch Linux users.

    Jump

  • I also don't see Swanstation going away any time soon, even if it gets no new features. It's pretty close to feature complete in the ways that matter anyway.

  • The future is NOT Self-Hosted, but Self-Sovereign

    Jump

  • I just overuse parantheses instead, as you noted. You know you're rambling when you have several layers of them, like I'm writing a conversation in Lisp.

  • AMD Kernel Graphics Driver Exceeds 5.9 Million Lines In Linux 6.16

    Jump

  • Most of this is auto-generated header files to be clear. Still, goes to show how many GPU variants they have support for in the kernel, going back 15+ years.

  • Recommendations for a source code hosting service

    Jump

  • Having a web UI is useful even if you're not using the extra tools. Not mandatory of course, but nice.

  • AccuWeather to discontinue free access to Core Weather API

    Jump

  • US only I suspect, and likely to be gutted by the Trump administration.

  • Can somebody explain the graphics stack? Vulkan, OpenGL, Magma, DirectX, SDL, Metal, Mesa, ... wat?

    Jump

  • I'm not really an expert, but I'll try and answer your questions one by one.

    Don’t VMs have a virtual GPU with a driver for that GPU in the guest that, I imagine, forwards the graphics instructions and routines to the driver on the host?

    Yes, this is what VirGL (OGL) and Venus (Vulkan) do. The latter works pretty well because Vulkan is more low level and better represents the underlying hardware so there is less of a performance overhead. However, this does mean you need to translate all APIs one by one, not just OGL and Vulkan, but also hardware decoding and encoding of videos, and compute, so it's a fair amount of work.

    Native contexts, in contrast, are basically the "real" host driver used in the guest, and they essentially pass through everything 1:1 to the host driver where the actual work is carried out. They aren't really like virtualisation extensions as the hardware doesn't need to support it AFAICT, just the drivers on both the host and the guest. There's a presentation and slides on native contexts vs virgl/venus which may be helpful.

    Where in that does Magma come in? My guess is that magma sits in the guest as the graphics driver and on the host before Mesa, but I know little about virtualisation outside of containers.

    To be honest, I don't fully understand the details either, but your interpretation seems more or less correct. From looking at the diagram on the MR it seems that it's a layer between the userspace graphics driver and the native context (virtgpu) layer on the guest side, which in turn communicates with another Magma layer on the host, and finally passes data to the host GPU driver, which may be Mesa but could also be other drivers as long as they implement Magma.

    The broader idea is to abstract implementation details, so applications and userspace drivers don't need to know the native context implementation details (other than interfacing with Magma). And the native context layer doesn't need to know which host gpu driver is being used, it just needs to interface with Magma.

  • Rate my Build: Long time since a hardware upgrade, and finally making the jump to Linux

    Jump

  • I'd probably get the 9070 XT over the 7080 XT, just for full performance FSR4 (there's some compatibility with it on Linux, but it's slower). Maybe even the non-XT model for the same reason.

    I feel like you might be able to do better price wise on the RAM, although I'm not up to date on current prices for DDR5.

    EDIT: I see you have an itx case, so maybe that limits your GPU options a bit.

  • Can somebody explain the graphics stack? Vulkan, OpenGL, Magma, DirectX, SDL, Metal, Mesa, ... wat?

    Jump

  • The other points have been answered, so I'll try and give a surface view of Magma. It's basically an abstraction layer for virtual GPU drivers used in VMs. Currently, you need specific implementations to handle all of the pathways between different types of VM guests and hosts, which gets complicated fast, and duplicates a lot of work. The idea is the Magma abstracts this away, and so host and guest GPU drivers only need to interface with Magma. Which means you can swap out different host OSes/GPU drivers and different guest OSes and GPU drivers, and as long as they interface with Magma, they should "just work".

    Of course, whether it will work out that way in practice remains to be seen. I think Google is using it internally but it's not in Mesa yet, so it may not even roll out widely. You can follow the MR if you want more detail or to see its progress.

    If you're wondering why Google is implementing this it appears to be for Fuschia and Android, and compatibility between those two and with desktop Linux, with Windows support also supported as an additional value add. Chromebooks in particular should benefit from this, since ChromeOS is being retired I believe.

    And as an aside, unlike some of the traditional GPU implementations you'd find in VMs, these are or will be pretty much just the normal graphics driver that you'd use on the host. They are generally called "native contexts" and have been implemented for AMD and Intel at the least, but only on non-Windows systems for now. These implementations alone, once they are widely supported, should result in near native GPU performance in VMs, without having to use GPU passthrough (I.e. passing through a physical GPU to the VM guest). So even without Magma there's some promising stuff happening, albeit mainly on the Linux host -> Linux guest pathway.

  • Texan Moved Fam to Russia to Flee Woke—Now He’s Headed to Ukraine Front Line

    Jump

  • And even if they could, it wouldn't save them, as being "one of the good ones" does nothing to prevent deportation or worse.

  • OpenAI just launched its new ChatGPT Agent that can make as many as 1 complicated cupcake order per hour, but even Sam Altman says you probably shouldn't trust it for 'high-stakes uses'

    Jump

  • I'm guessing it's the AI agent stuff. Which at the moment is literally just automating browsing through a website.

    Apparently there will be APIs to do this in the future. Ironically, AI wouldn't even be needed for that to be useful.