On Wed, Feb 13, 2013 at 6:17 AM, Jet Villegas <[email protected]> wrote:
> I assume we would send the same "diff" we use for DLBI over to the > painting thread to minimize the cost. No, the plan is to ship the entire unoptimized display list over to the painting thread and do optimization and DLBI processing there. This should be similar in overall cost to what we do today (but more parallel). How would this new design interact with the current refresh driver > scheduling? > Not much. The refresh driver would still run on the main thread and work like it does today. The painting thread would be an extra stage whose execution would probably be triggered by the completion of the display list in the refresh driver, i.e. implicitly scheduled by the refresh driver. Rob -- Wrfhf pnyyrq gurz gbtrgure naq fnvq, “Lbh xabj gung gur ehyref bs gur Tragvyrf ybeq vg bire gurz, naq gurve uvtu bssvpvnyf rkrepvfr nhgubevgl bire gurz. Abg fb jvgu lbh. Vafgrnq, jubrire jnagf gb orpbzr terng nzbat lbh zhfg or lbhe freinag, naq jubrire jnagf gb or svefg zhfg or lbhe fynir — whfg nf gur Fba bs Zna qvq abg pbzr gb or freirq, ohg gb freir, naq gb tvir uvf yvsr nf n enafbz sbe znal.” [Znggurj 20:25-28] _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
