Anton Altaparmakov <aia21@xxxxxxxxx> wrote: > On 14 Apr 2008, at 13:46, Szabolcs Szakacsits wrote: >> On Mon, 14 Apr 2008 Anton Altaparmakov wrote: >>> (and under no-one I include the OOM killer for example!) >> >> The OOM killer can be configured and if the fs still uses too much >> memory >> then probably it's better to be killed/restarted with journaling >> support. >> The important here would be the kernel finally fixing the non-sync >> behavior >> when it clams to do so (see recent kernel threads). > > You don't get the point. Any process in the system can be using too > much memory and trigger the OOM killer even when the FS is behaving > just fine... Just set /proc/$pid/oom_adj to -17. -- 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
