Messages in this thread | | | Date | Fri, 08 Jun 2012 02:57:47 -0400 | From | KOSAKI Motohiro <> | Subject | Re: [PATCH 0/5] Some vmevent fixes... |
| |
(6/8/12 2:54 AM), Pekka Enberg wrote: > On Fri, Jun 8, 2012 at 6:55 AM, KOSAKI Motohiro > <kosaki.motohiro@gmail.com> wrote: >>> For some cases, yes, but probably not for all. >>> >>> For example, if userspace doesn't know about "about to swap real soon" >>> condition, it can continue to grow its caches making >>> fallocate(VOLATILE) pretty much useless. >> >> Fair enough. But, Please consider your scenario don't need vmevent(2), >> cat /proc/meminfo works enough. Only dropping activity need a quick work >> and just in time notification. cache growing limitation don't need. > > Why do you keep bringing this up? Yes, you might get away with polling > /proc/meminfo or /proc/vmstat for some specific cases. It does not > make it a proper generic solution to the problem "vmevent" ABI tries > to address.
Guys, current vmevent _is_ a polling interface. It only is wrapped kernel timer.
| |