And that's the reason I added the pool: to avoid the cost of constantly faulting pages into new shm areas. I profiled window resizing under Weston and got the same result.
Kristian > On Mar 14, 2016, at 7:20 AM, gtk+ (GNOME Bugzilla) <[email protected]> wrote: > > Comment # 17 on bug 763350 from Ray Strode [halfline] > (In reply to Christian Hergert from comment #9) > > I was curious about the raw memfd costs, so put together an informative > > test: > > > > - memfd_create() > > - ftruncate(2*page_size) > > - mmap() > > - page fault all pages > > - munmap() > > - close() > > > > The cost for all of the above is about .06 msec. So not really that bad. > > Interestingly, half of the time is spent on close()! > > are you accounting for faulting in the compositor too? if you run, > > $ ./test-panel & > $ sysprof-cli -p $! sysprof-output > > then open and close the panels like a billion times, then switch back to the > terminal and hit ctrl-c > > then run > > $ sysprof sysprof-output > > what's at the top of your profile ? I see most of the time spent in > sse2_fill/page_fault/shmem_fault, but for me the animations are 60 fps anyway. > I'm curious what your sysprof profile looks like. > You are receiving this mail because: > You are on the CC list for the bug. > _______________________________________________ > wayland-bugs mailing list > [email protected] > https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
_______________________________________________ wayland-bugs mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
