Re: Andrea VM changes

From: Jonathan Lundell (linux_at_lundell-bros.com)
Date: 08/31/03

  • Next message: John Levon: "[PATCH] OProfile: correct CPU type for x86-64" 
    Date:	Sun, 31 Aug 2003 12:08:56 -0700
To: linux-kernel@vger.kernel.org

    At 8:51am -0700 8/31/03, Dan Kegel wrote:
    >In the test-and-measurement system I'm developing,
    >it turned out the sanest thing to do with OOM conditions
    >was to consider them user errors, and to handle them
    >by dumping memory usage info about processes and slab caches,
    >then halt. It's been very helpful because it turns flaky
    >conditions into rock-solid failures. Too bad this drastic
    >approach isn't appropriate for general use.

    Likewise in an HA environment, if you've got a standby node
    available, we prefer to fail over on an oom condition or (or an oops,
    for that matter) than to try to continue running in some randomly
    crippled way. The node in question can then reboot and return to
    service as a standby.

    Ideally, we'd have a notifier that would be triggered for every
    unanticipated process kill (oom, oops, whatever). 

    -- 
/Jonathan Lundell.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: John Levon: "[PATCH] OProfile: correct CPU type for x86-64"

    Relevant Pages

    • Re: Cant make use of swap memory in 2.6.7-bk19
      ... >> then propagated down the call chain and eventually passed as an argument ... >> OOM conditions based on the wiredness of the failing allocation. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Andrea VM changes
      ... > it turned out the sanest thing to do with OOM conditions ... > by dumping memory usage info about processes and slab caches, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)