DisplayLink CPU USAGE CRITICAL UBUNTU 16.04

JB_Harris · 04-20-2018, 02:29 PM

I think this will always be a problem when you're doing video rendering in software vs on hardware (GPU). I'm not an expert, but I'm fairly certain that all of the frame rendering, window treatments & management, shadows, transparency, positioning, etc... on these DisplayLink devices has to be done by the HOST PC's CPU and then transferred as raw frames/bitmaps to the monitor....I don't think anything can be offloaded to the screen to handle since the interface just doesn't understand it.

It reminds me of the old "WinModems" from back in the late 90s. They were modems where all of the modulation & signal processing was done in the CPU instead of onboard microprocessors. This made them very cheap, but it meant they weren't compatible with other operating systems, and it meant that you had to have a relatively fast CPU in order to handle higher speeds (like 56k).

Trade offs.

04-20-2018, 02:29 PM	#4
JB_Harris Junior Member Join Date: Apr 2018 Posts: 1	CPU acting as GPU I think this will always be a problem when you're doing video rendering in software vs on hardware (GPU). I'm not an expert, but I'm fairly certain that all of the frame rendering, window treatments & management, shadows, transparency, positioning, etc... on these DisplayLink devices has to be done by the HOST PC's CPU and then transferred as raw frames/bitmaps to the monitor....I don't think anything can be offloaded to the screen to handle since the interface just doesn't understand it. It reminds me of the old "WinModems" from back in the late 90s. They were modems where all of the modulation & signal processing was done in the CPU instead of onboard microprocessors. This made them very cheap, but it meant they weren't compatible with other operating systems, and it meant that you had to have a relatively fast CPU in order to handle higher speeds (like 56k). Trade offs.