https://bugzilla.kernel.org/show_bug.cgi?id=198511
--- Comment #26 from Christian König (christian.koe...@amd.com) --- (In reply to Barto from comment #25) > but this advice seems to be a "cheat mode/workaround", it doesn't explain > why your commit triggers this problem with firefox 57 when > "layers.acceleration.force-enabled" option is disabled in firefox ( which is > the default value ), Well, actually it explains perfectly what is going wrong here :) My huge page patches makes memory accesses faster for the price of making allocating memory more costly. E.g. by using 2M pages instead of 4K you improve some hardware path by the factor of 512. Now what I see when I look at your numbers is that user space allocated and freed (13608−4514)*2M = 18.1GB of memory while playing youtube videos!. This means that either the application or the driver stack is doing something very very stupid. Instead of using buffers round robin they are allocating them, using them once and then freeing them again. As a band aid I will try to fix our algorithm when pages are freed again, but in general the driver stack or application should be fixed to not do that. Probably best if you open up a bug report on http://bugs.freedesktop.org/ so that somebody can investigate what userspace is doing here. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
