Hi, On Sat 22-06-13 01:27:43, Minchan Kim wrote: > > > Question. > > > > > > 1. user: set critical edge > > > 2. kernel: memory is tight and trigger event with critical > > > 3. user: kill a program when he receives a event > > > 4. kernel: memory is very tight again and want to trigger a event > > > with critical but fail because last_level was critical and it was edge. > > > > > > Right? > > > > yes, this is the risk of the edge triggering and the user has to be > > prepared for that. I still think that it makes some sense to have the > > two modes. > > I'm not sure it's good idea. > How could user overcome above problem? Well, if the interface is proposed to workaround issues of the current implementation then it is surely not a good path. I was referring to a concept of edge triggering which makes some sense to me. Consider one shot actions that should start/stop a certain action when the level changes (e.g. very popular notification to admin). [...] -- Michal Hocko SUSE Labs -- 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/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>