On Wed, May 2, 2012 at 8:04 AM, Minchan Kim <minchan@xxxxxxxxxx> wrote: > I think hardest problem in low mem notification is how to define _lowmem situation_. > We all guys (server, desktop and embedded) should reach a conclusion on define lowmem situation > before progressing further implementation because each part can require different limits. > Hopefully, I want it. > > What is the best situation we can call it as "low memory"? Looking at real-world scenarios, it seems to be totally dependent on userspace policy. On Wed, May 2, 2012 at 8:04 AM, Minchan Kim <minchan@xxxxxxxxxx> wrote: > As a matter of fact, if we can define it well, I think even we don't need vmevent ABI. > In my opinion, it's not easy to generalize each use-cases so we can pass it to user space and > just export low attributes of vmstat in kernel by vmevent. > Userspace program can determine low mem situation well on his environment with other vmstats > when notification happens. Of course, it has a drawback that userspace couples kernel's vmstat > but at least I think that's why we need vmevent for triggering event when we start watching carefully. Please keep in mind that VM events is not only about "low memory" notification. The ABI might be useful for other kinds of VM events as well. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>