<div dir="ltr"><div class="gmail_extra"><br /><div class="gmail_quote">On Wed, Sep 25, 2013 at 12:15 AM, Daniel Farina
<spandir="ltr"><<a href="mailto:daniel@heroku.com" target="_blank">daniel@heroku.com</a>></span> wrote:<br
/><blockquoteclass="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":5dt"
style="overflow:hidden">Enable the memcg OOM killer only for user faults, where it's really the<br /> only option
available.</div></blockquote></div><br/></div><div class="gmail_extra">Is this really a big deal? I would expect most
faultsto be user faults. <br /><br /></div><div class="gmail_extra">It's certainly a big deal that we need to ensure we
canhandle ENOMEM from syscalls and library functions we weren't expecting to return it. But I don't expect it to
actuallyreduce the OOM killing sprees by much.<br /></div><div class="gmail_extra"><br clear="all" /><br />-- <br
/>greg<br/></div></div>