|
From: Josef W. <Jos...@gm...> - 2008-01-04 01:59:50
|
On Friday 04 January 2008, Julian Seward wrote: > At least the current Callgrind scheme localises its complexity > in one place. The performance aspects are not a big deal, because > we can make the scheduler polling-aware - let it decide when to poll, > and, if the intervals get too close together, increase the scheduling > quantum (or something similar) so as to limit the polling rate. Yes, that sounds fine. > The only real problem is the case where all client threads are > sleeping. What do you suggest as possible solution? Does the complexity issue also cover "just" a VG-specific signal to trigger polling for an interactive command? Hmm... how does this work at all? If there is a signal from another process, how can VG decide whether it is for the client or VG itself? For VG-internal signals, this is no issue... Josef > > J > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |