- Original Message -
> The X server has limited throttle support on the server side,
> but doing this in the client has some benefits:
>
> 1) X server throttling is per client. Client side throttling can be
> done
> per drawable.
>
> 2) It's easier to control the throttling based on what
On Mit, 2011-10-12 at 11:35 +0200, Thomas Hellstrom wrote:
> Thanks for reviewing, Michel.
> On 10/11/2011 05:29 PM, Michel Dänzer wrote:
> > On Die, 2011-10-11 at 15:44 +0200, Thomas Hellstrom wrote:
> >
> >> The X server has limited throttle support on the server side,
> >> but doing this in
Thanks for reviewing, Michel.
On 10/11/2011 05:29 PM, Michel Dänzer wrote:
On Die, 2011-10-11 at 15:44 +0200, Thomas Hellstrom wrote:
The X server has limited throttle support on the server side,
but doing this in the client has some benefits:
1) X server throttling is per client. Client si
On Die, 2011-10-11 at 15:44 +0200, Thomas Hellstrom wrote:
> The X server has limited throttle support on the server side,
> but doing this in the client has some benefits:
>
> 1) X server throttling is per client. Client side throttling can be done
> per drawable.
>
> 2) It's easier to control
The X server has limited throttle support on the server side,
but doing this in the client has some benefits:
1) X server throttling is per client. Client side throttling can be done
per drawable.
2) It's easier to control the throttling based on what client is run,
for example using "driconf".
