* Kirill A. Shutemov <kirill@xxxxxxxxxxxxx> [2009-12-27 04:08:58]: > This patchset introduces eventfd-based API for notifications in cgroups and > implements memory notifications on top of it. > > It uses statistics in memory controler to track memory usage. > > Output of time(1) on building kernel on tmpfs: > > Root cgroup before changes: > make -j2 506.37 user 60.93s system 193% cpu 4:52.77 total > Non-root cgroup before changes: > make -j2 507.14 user 62.66s system 193% cpu 4:54.74 total > Root cgroup after changes (0 thresholds): > make -j2 507.13 user 62.20s system 193% cpu 4:53.55 total > Non-root cgroup after changes (0 thresholds): > make -j2 507.70 user 64.20s system 193% cpu 4:55.70 total > Root cgroup after changes (1 thresholds, never crossed): > make -j2 506.97 user 62.20s system 193% cpu 4:53.90 total > Non-root cgroup after changes (1 thresholds, never crossed): > make -j2 507.55 user 64.08s system 193% cpu 4:55.63 total > > Any comments? Thanks for adding the documentation, now on to more critical questions 1. Any reasons for not using cgroupstats? 2. Is there a user space test application to test this code. IIUC, I need to write a program that uses eventfd(2) and then passes the eventfd descriptor and thresold to cgroup.*event* file and then the program will get notified when the threshold is reached? -- Balbir _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
