From: Daryll S. <da...@va...> - 2001-01-29 00:45:19
|
On Mon, Jan 29, 2001 at 10:33:30AM +1100, Gareth Hughes wrote: > Simple answer: every time you move the mouse or hit a key, the X server > grabs the hardware lock. Yep, even when you're playing fullscreen Quake > and it doesn't have to do anything. The 3D driver then has to go > through the whole lock acquisition process again, which causes the input > lag you describe. I've almost finished a preliminary patch for the > Radeon driver that fixes this problem, which I'll post to the list so > people can comment. Once everyone's happy with the solution, we can > port this to the other drivers. David S. Miller was bugging me about > this, as he submitted a bug report well over six months ago and it > hasn't been addressed... Actually, the tdfx driver doesn't take the lock to do mouse/keyboard I/O. Unfortunetly, he said he's having the same problem when he runs with the tdfx driver. The fact that his disk is churning at the same time makes me wonder if perhaps he's memory starved. Q3A needs substantial memory and then we add the X server on top of that. (Don't believe the ps/top values for memory, they don't report the amount of physical memory in use because you're counting board memory/registers). Then you've got window manager, desktop, etc which all eat RAM. If your system has <128MB that could be the problem. - |Daryll |