> Its not expected to be too long, we tend to get vblank every 16ms. > With using usleep_range with min and max as 1-2ms, we have observed that this function consuming 4ms to 17ms. > Having 10ms sleep timer, we might tend to be blocking for 6ms in some > cases.(from the above data) Moreover 10ms usleep doesn't guarantee > that we get a chance to execute after 10ms, it might get increased due to scheduling. So ideal solution would be to use useep_range which uses hrtimers. Can you please do proper quoting when replying? It makes it fairly hard to figure out what's your response when you reply in-line, especially in more complicated threads. And top-posting isn't an option either, especially for more in-depth discussions where the different issues need to be treated as separate points. You need a real mail client for this, Outlook won't cut it. Jesse is floating slides internal with all the details and tons of links to resources. Sure will take care of this in future. Thanks and Regards, Arun R Murthy ------------------ _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
