Skip to contentSkip to conversation

weird X problem - priority inversion?

DISCUSSION Lee Revell 5 participants 10 messages Apr 13, 2005 – May 27, 2005

lore
Share & tools
lore

Lee Revell

author
#0 lore raw

I am having a problem with the RT preempt kernels where xscreensaver will cause the X server to consume excessive CPU, starving other processes. This should not happen as xscreensaver runs at the highest nice value. It seems that there's some kind of priority inversion happening between the high prio X server and low prio xscreensaver.

This seems like an X problem to me, but could the kernel be involved?

Lee

#1 lore raw

does this still occur with the latest tree? (.47-05 or later)

Ingo

Quoted 9 lines · Lee Revell

I am having a problem with the RT preempt kernels where xscreensaver will cause the X server to consume excessive CPU, starving other processes. This should not happen as xscreensaver runs at the highest nice value. It seems that there's some kind of priority inversion happening between the high prio X server and low prio xscreensaver.

This seems like an X problem to me, but could the kernel be involved?

Lee

#2 lore raw

remember that the low pri screensaver is just generating the image to be displayed, it's the high pri X server that's actually doing the work to display it.

David Lang

Quoted 21 lines · Ingo Molnar

does this still occur with the latest tree? (.47-05 or later)

Ingo

Quoted 9 lines · Lee Revell

I am having a problem with the RT preempt kernels where xscreensaver will cause the X server to consume excessive CPU, starving other processes. This should not happen as xscreensaver runs at the highest nice value. It seems that there's some kind of priority inversion happening between the high prio X server and low prio xscreensaver.

This seems like an X problem to me, but could the kernel be involved?

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/

Signature · 2 lines
There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.
 -- C.A.R. Hoare
author
#3 lore raw
Quoted 4 lines · David Lang

remember that the low pri screensaver is just generating the image to be displayed, it's the high pri X server that's actually doing the work to display it.

Understood. It still seems like a bug that a lowly screensaver can
wedge the X server to the point that it consumes all available CPU. This is a DoS - you can barely ssh in.

Lee

author
#4 lore raw
In reply to David Lang
Quoted 3 lines · David Lang

remember that the low pri screensaver is just generating the image to be displayed, it's the high pri X server that's actually doing the work to display it.

Then there needs to be some mechanism to handle it, either in X or the kernel. Other OSes do not require you to turn off the screensaver to avoid a DoS - they do the obvious thing and run the screensaver at the lowest priority.

The problem may be software 3D rendering (I did not have the VIA driver
enabled as I did not realize it was in the kernel yet). Maybe the X
server should do the work in a low priority thread. But it sure shouldn't DoS the system. Other OSes do not have this problem.

Lee

#5 lore raw
Quoted 10 lines · Lee Revell
Quoted 3 lines · David Lang

remember that the low pri screensaver is just generating the image to be displayed, it's the high pri X server that's actually doing the work to display it.

Then there needs to be some mechanism to handle it, either in X or the kernel. Other OSes do not require you to turn off the screensaver to avoid a DoS - they do the obvious thing and run the screensaver at the lowest priority.

Quoted 4 lines

The problem may be software 3D rendering (I did not have the VIA driver
enabled as I did not realize it was in the kernel yet). Maybe the X
server should do the work in a low priority thread. But it sure shouldn't DoS the system. Other OSes do not have this problem.

Actually they don't (or at least didn't the last time I took windows training), if you have a CPU intensive screen saver on a windows server it will seriously load down the box when it kicks in.

David Lang

Signature · 2 lines
There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.
 -- C.A.R. Hoare
author
#6 lore raw
Quoted 12 lines · David Lang
Quoted 10 lines · Lee Revell
Quoted 3 lines · David Lang

remember that the low pri screensaver is just generating the image to be displayed, it's the high pri X server that's actually doing the work to display it.

Then there needs to be some mechanism to handle it, either in X or the kernel. Other OSes do not require you to turn off the screensaver to avoid a DoS - they do the obvious thing and run the screensaver at the lowest priority.

Quoted 8 lines
Quoted 4 lines

The problem may be software 3D rendering (I did not have the VIA driver
enabled as I did not realize it was in the kernel yet). Maybe the X
server should do the work in a low priority thread. But it sure shouldn't DoS the system. Other OSes do not have this problem.

Actually they don't (or at least didn't the last time I took windows training), if you have a CPU intensive screen saver on a windows server it will seriously load down the box when it kicks in.

That was a problem in the NT 4.0 days, but not lately.

Lee

#7 lore raw
Quoted 18 lines · Lee Revell
Quoted 17 lines · David Lang
Quoted 14 lines · Lee Revell
Quoted 3 lines · David Lang

remember that the low pri screensaver is just generating the image to be displayed, it's the high pri X server that's actually doing the work to display it.

Then there needs to be some mechanism to handle it, either in X or the kernel. Other OSes do not require you to turn off the screensaver to avoid a DoS - they do the obvious thing and run the screensaver at the lowest priority.

The problem may be software 3D rendering (I did not have the VIA driver
enabled as I did not realize it was in the kernel yet). Maybe the X
server should do the work in a low priority thread. But it sure shouldn't DoS the system. Other OSes do not have this problem.

Quoted 5 lines
Quoted 3 lines

Actually they don't (or at least didn't the last time I took windows training), if you have a CPU intensive screen saver on a windows server it will seriously load down the box when it kicks in.

That was a problem in the NT 4.0 days, but not lately.

Ok, it has been a while since I had windows training (and I DON'T miss it ;-)

David Lang

Signature · 2 lines
There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.
 -- C.A.R. Hoare
#8 lore raw
In reply to Ingo Molnar
Quoted 13 lines · Ingo Molnar

does this still occur with the latest tree? (.47-05 or later)

Ingo

Quoted 7 lines · Lee Revell

I am having a problem with the RT preempt kernels where xscreensaver will cause the X server to consume excessive CPU, starving other processes. This should not happen as xscreensaver runs at the highest nice value. It seems that there's some kind of priority inversion happening between the high prio X server and low prio xscreensaver.

This seems like an X problem to me, but could the kernel be involved?

I have a problem with X too. It could be the same.

I have a test program which made a loop in RT to mesure the system perturbation. It works finely in a tty environment.
When I run it in an X environment ( xterm ), I get something like if I click the Enter key. If I open a new xterm, this is the active window which receive these events. These events stop when the program stop.

author
#9 lore raw
In reply to Ingo Molnar
Quoted 1 line · Ingo Molnar

does this still occur with the latest tree? (.47-05 or later)

I'll retest with the latest version. It's still present in 2.6.12-rc4-RT-V0.7.47-01.

Do you think the kernel could be involved? It's looking more like an X problem to me.

Lee