On Tue, 19 Feb 2008 09:00:08 -0600 Paul Jackson <pj@xxxxxxx> wrote: > Depending on what we're trying to do: > 1) warn applications of swap coming soon (your case), > 2) show how close we are to swapping, > 3) show how much swap has happened already, > 4) kill instantly if try to swap (my hpc case), > 5) measure file i/o caused by memory pressure, or > 6) perhaps other goals, > we will need to hook different places in the kernel. > > It may well be that your hooks for embedded are simply in different > places than my hooks for HPC. If so, that's fine. Don't forget the "hooks for desktop" :) Basically in all situations, the kernel needs to warn at the same point in time: when the system is about to run out of RAM for anonymous pages. In the desktop case, that leads to swapping (and programs can free memory). In the embedded case, it leads to OOM (and a management program can kill or restart something else, or a program can restart itself). In the HPC case, it leads to swapping (and a management program can kill or restart something else). I do not see the kernel side being different between these situations, only userspace reacts differently in the different scenarios. Am I overlooking something? -- All Rights Reversed - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
