News: 0001605058

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Mesa 26.0 RADV Lands Dedicated Transfer-Only Queue Using SDMA

([Radeon] 6 Hours Ago RADV Transfer Queue Via SDMA)


There is another open-source Radeon Vulkan driver (RADV) improvement to look forward to in the upcoming [1]Mesa 26.0 release that was worked on by one of Valve's Linux graphics driver developers.

Timur Kristóf in addition to his [2]recent work improving old AMD GCN 1.0/1.1 GPUs has finally pushed his dedicated transfer-only queue patches using the SDMA engine over the finish line. Since October 2023 was the merge request [3]radv: Add a dedicated transfer-only queue using SDMA .

That was motivated by [4]this 2019 bug report (and since 2018 in the original BugZilla thread) requesting a dedicated transfer-only queue to help with resource streaming and memory defragmentation. The argument back then was that the AMDVLK driver supported such functionality as well as the NVIDIA proprietary Vulkan driver. Even going back years various Vulkan apps/back-ends supported using transfer queues while since 2023, Timur has been battling the RADV support.

[5]

The code merged for Mesa 26.0 has the RADV dedicated transfer queue support working on GFX9 (Vega) and newer GPUs. Enabling this feature currently requires the RADV_PERFTEST=transfer_queue environment variable to activate. The DXVK Direct3D-on-Vulkan layer is among the software able to benefit from the Vulkan transfer queues support although there are no performance/benchmark numbers noted in that merge request for quantifying the benefit of the new functionality.

Mesa 26.0 stable should be out in February with the feature freeze / code branching expected for next week.



[1] https://www.phoronix.com/search/Mesa+26.0

[2] https://www.phoronix.com/news/Timur-More-Old-AMDGPU-2026

[3] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25594

[4] https://gitlab.freedesktop.org/mesa/mesa/-/issues/850

[5] https://www.phoronix.com/image-viewer.php?id=2026&image=radv_transfer_queue_lrg



When alerted to an intrusion by tinkling glass or otherwise, 1) Calm
yourself 2) Identify the intruder 3) If hostile, kill him.

Step number 3 is of particular importance. If you leave the guy alive
out of misguided softheartedness, he will repay your generosity of spirit
by suing you for causing his subsequent paraplegia and seek to force you
to support him for the rest of his rotten life. In court he will plead
that he was depressed because society had failed him, and that he was
looking for Mother Teresa for comfort and to offer his services to the
poor. In that lawsuit, you will lose. If, on the other hand, you kill
him, the most that you can expect is that a relative will bring a wrongful
death action. You will have two advantages: first, there be only your
story; forget Mother Teresa. Second, even if you lose, how much could
the bum's life be worth anyway? A Lot less than 50 years worth of
paralysis. Don't play George Bush and Saddam Hussein. Finish the job.
-- G. Gordon Liddy's "Forbes" column on personal security