linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: David Rientjes <rientjes@google.com>
Cc: Michal Hocko <mhocko@suse.cz>,
	linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org,
	Tim Hockin <thockin@google.com>,
	Kamil Yurtsever <kyurtsever@google.com>
Subject: Re: [Lsf-pc] [LSF/MM ATTEND, TOPIC] memcg topics and user defined oom policies
Date: Sun, 12 Jan 2014 10:31:00 -0800	[thread overview]
Message-ID: <1389551460.7596.4.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1401101318160.21486@chino.kir.corp.google.com>

On Fri, 2014-01-10 at 13:23 -0800, David Rientjes wrote:
> On Wed, 8 Jan 2014, Michal Hocko wrote:
> 
> > David was proposing memory reserves for memcg userspace OOM handlers.
> > I found the idea interesting at first but I am getting more and more
> > skeptical about fully supporting oom handling from within under-oom
> > group usecase. Google is using this setup and we should discuss what is
> > the best approach longterm because the same thing can be achieved by a
> > proper memcg hierarchy as well.
> > 
> > While we are at memcg OOM it seems that we cannot find an easy consensus
> > on when is the line when the userspace should be notified about OOM [1].
> > 
> > I would also like to continue discussing user defined OOM policies.
> > The last attempt to resurrect the discussion [2] ended up without any
> > strong conclusion but there seem to be some opposition against direct
> > handling of the global OOM from userspace as being too subtle and
> > dangerous. Also using memcg interface doesn't seem to be welcome warmly.
> > This leaves us with either loadable modules approach or a generic filter
> > mechanism which haven't been discussed that much. Or something else?
> > I hope we can move forward finally.
> > 
> 
> Google is interested in this topic and has been the main motivation for 
> userspace oom handlers; we would like to attend for this discussion.
> 
> David Rientjes <rientjes@google.com>
> Tim Hockin <thockin@google.com>, systems software, senior staff
> Kamil Yurtsever <kyurtsever@google.com>, systems software

OK, so please don't do this.  Please send in Topic/attend requests as
per the CFP.  Doing this gives us no way to judge the merits of the
request and, administratively, it gets lost because the way I populate
the attendance request table is to filter on the topic/attend requests
and then fold the threads up to the head.

Please send in one separate topic/attend email authored by the person
who wants to attend.

Thanks,

James


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2014-01-12 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 15:11 Michal Hocko
2014-01-10 21:23 ` David Rientjes
2014-01-12 18:31   ` James Bottomley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1389551460.7596.4.camel@dabdike.int.hansenpartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=kyurtsever@google.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=mhocko@suse.cz \
    --cc=rientjes@google.com \
    --cc=thockin@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox