Skip to content

Damian Chiliński

My feedback

3 results found

  1. 17 votes
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damian Chiliński supported this idea  · 
  2. 121 votes
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damian Chiliński supported this idea  · 
  3. 441 votes
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damian Chiliński supported this idea  · 
    An error occurred while saving the comment
    Damian Chiliński commented  · 

    CPU utilization of DisplayLink on Linux strongly depends on particular application that is used. I noticed heavy CPU usage when compiz (compositor) is used comparing to when it's not. Also using remote Xorg display powered by DL device (export DISPLAY=10.0.0.2:0 on remote machine, when 10.0.0.2 machine is using DL) results in insane CPU load. There's a lot of cases that make DL display struggle significantly. However I think it's related to number of draw operations issues by certain software, comparing to others.

Feedback and Knowledge Base