RADV Reworking Pipeline Emitting To Improve CPU Usage

[phoronix]

Phoronix: RADV Reworking Pipeline Emitting To Improve CPU Usage

While using Vulkan lowers the CPU utilization compared to OpenGL, in our testing of NVIDIA versus the open-source Radeon drivers we generally have found the red team's drivers to consume more CPU resources. Thus it's good to hear that RADV co-conspirator Bas Nieuwenhuizen is working on reworking how this Radeon Vulkan driver handles pipeline emitting...

http://www.phoronix.com/scan.php?page=news_item&px=RADV-Pipeline-Emitting

[pal666]

"with the healthy competition thanks to the newly-opened AMDVLK driver."
open amdvlk actually means less competition - it allows just copying its code to radv

[M@yeulC]

"with the healthy competition thanks to the newly-opened AMDVLK driver."
open amdvlk actually means less competition - it allows just copying its code to radv

Which is arguably the best kind of competitor :P

[raonlinux]

"with the healthy competition thanks to the newly-opened AMDVLK driver."
open amdvlk actually means less competition - it allows just copying its code to radv

Also the other way, copying from radv to amdvlk.

[airlied]

"with the healthy competition thanks to the newly-opened AMDVLK driver."
open amdvlk actually means less competition - it allows just copying its code to radv

Why would we want to bloat radv like that?

Dave.

[slacka]

RAVD is based on Intel's ANV. Will Intel GPUs be able to benefit from this optimization or is it Radeon specific?

[BNieuwenhuizen]

RAVD is based on Intel's ANV. Will Intel GPUs be able to benefit from this optimization or is it Radeon specific?

It is just some code restructuring in radv in non-shared code, so anv will not benefit. The principle behind it might or might not benefit anv, would need to check if they do it already.

[duby229]

Why would we want to bloat radv like that?

Dave.

Most of us have no idea what you mean. Is amdvlk bloated? And if not, if amdvlk has some good code that could potentially be used in radv would you use it? (Or is it more a coding style thing?)

[airlied]

Most of us have no idea what you mean. Is amdvlk bloated? And if not, if amdvlk has some good code that could potentially be used in radv would you use it? (Or is it more a coding style thing?)

You can't just copy the code between drivers, you can use the other driver for ideas but the codebases are in no way compatible, you still have to rewrite code, e.g. amdvlk has the xgl shim on top of pal, pal defines all its own API, radv has none of that separation.

They definitely have a lot larger code base doing mostly the same things, so bloat definitely exists, it may exist for reasons of course that only affect amdvlk.

Dave.

[bridgman]

They definitely have a lot larger code base doing mostly the same things, so bloat definitely exists, it may exist for reasons of course that only affect amdvlk. Dave.

It's not there so much for AMDVLK itself - it's there in order to let one set of core code support a number of different OS/API combinations.