Re: [PATCH 0/5] Some vmevent fixes...

[KOSAKI Motohiro]

(6/8/12 2:54 AM), Pekka Enberg wrote:
> On Fri, Jun 8, 2012 at 6:55 AM, KOSAKI Motohiro
> <kosaki.motohiro@xxxxxxxxx>  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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/