On Mon, 2006-01-23 at 22:10 +0100, Paolo Ornati wrote:
> On Mon, 23 Jan 2006 15:59:38 -0500
> Lee Revell <[email protected]> wrote:
>
> > > Maybe this is normal and depends on the way X sleeps or something...
> > >
> >
> > Because the scheduler favors interactive tasks (aka those which spend a
> > large % of time waiting on external events) and X is only considered
> > interactive when the mouse is being moved. When glxgears is running
> > it's CPU bound and is therefore penalized.
>
> ??
>
> The reverse... lower priority number means BETTER priority. So Actually
> X is penalized when I'm moving the mouse.
>
> And running "glxgears" doesn't make X CPU bounded if direct rendering
> is enabled -- it is GPU bounded...
>
> In fact I can run "glxgears" and still have 97% of IDLE CPU time.
>
Ah, never mind, I misread your report then, I was thinking in terms of
RT priorities...
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
