i found it not to be a big deal to just redraw the cursor without any delay. this is usualy very quick anyway. the only exception is when another process holds onto the drawlock for a long time because of some expensive operation (poly drawing). and in that case, the cursor draw process will be queued on the drawlock and will be scheduled right after the other process releases the lock.
the important thing is that the cursor drawing doesnt block mouse event processing and delivery to userspase. (which still happens at interrupt time) i think the HZ value shouldnt matter. because the redraw interrupt was triggered every 33ms. the resolution of the time base should not be important in that case. the effect is mostly visible if you have one process doing lots of poly draws in a tight loop. then the cursor redraw interrupt will miss the drawlock most of the time and the cursor started rocking arround at a rate of like 1HZ on my x200. the mouse events themselves arent affected, its just the redrawing of the software cursor. -- cinap
