linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org
Subject: [LSF/MM TOPIC ATTEND]
Date: Tue, 6 Jan 2015 17:14:35 +0100	[thread overview]
Message-ID: <20150106161435.GF20860@dhcp22.suse.cz> (raw)

Hi,
I would like to attend this year (2015) LSF/MM conference. I am
particularly interested in the MM track. I would like to discuss (among
other topics already suggested) the following topics:
General MM topics:
- THP success rate has become one of the metric for reclaim/compaction
  changes which I feel is missing one important aspect and that is
  cost/benefit analysis. It might be better to have more THP pages in
  some loads but the whole advantage might easily go away when the
  initial cost is higher than all aggregated saves. When it comes to
  benchmarks and numbers we are usually missing the later.
  This becomes even more an issue with memcg when close to the limit.
  Does it make sense to do a heavy reclaim (with THP size target) to
  fulfill THP allocations? If not memcg acts against the global MM and
  ruins the effort, on the other hand reclaiming 512 pages can take
  quite some time.
  The memcg part could be worked around by either precharging THP pages
  or reclaiming only clean page cache pages which would handle most
  usecases IMO but it would be better to think about a !memcg solution. Do
  we really want to allocate THP pages unconditionally or rather build
  them up if it seems worthwhile?

- As it turned out recently GFP_KERNEL mimicing GFP_NOFAIL for !costly
  allocation is sometimes kicking us back because we are basically
  creating an invisible lock dependencies which might livelock the whole
  system under OOM conditions.
  That leads to attempts to add more hacks into the OOM killer
  which is tricky enough as is. Changing the current state is
  quite risky because we do not really know how many places in the
  kernel silently depend on this behavior. As per Johannes attempt
  (http://marc.info/?l=linux-mm&m=141932770811346) it is clear that
  we are not yet there! I do not have very good ideas how to deal with
  this unfortunatelly...

And as a memcg co-maintainer I would like to also discuss the following
topics.
- We should finally settle down with a set of core knobs exported with
  the new unified hierarchy cgroups API. I have proposed this already
  http://marc.info/?l=linux-mm&m=140552160325228&w=2 but there is no
  clear consensus and the discussion has died later on. I feel it would
  be more productive to sit together and come up with a reasonable
  compromise between - let's start from the begining and keep useful and
  reasonable features.
  
- kmem accounting is seeing a lot of activity mainly thanks to Vladimir.
  He is basically the only active developer in this area. I would be
  happy if he can attend as well and discuss his future plans in the
  area. The work overlaps with slab allocators and slab shrinkers so
  having people familiar with these areas would be more than welcome
-- 
Michal Hocko
SUSE Labs

--
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:[~2015-01-06 16:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 16:14 Michal Hocko [this message]
2015-01-06 23:27 ` Greg Thelen
2015-01-07 14:28   ` Michal Hocko
2015-01-07 18:54     ` Greg Thelen
2015-01-07 19:00     ` Greg Thelen
2015-01-14 21:27     ` Andrea Arcangeli
2015-01-15 14:06       ` Michal Hocko
2015-01-15 20:58         ` Andrea Arcangeli
2015-01-07  8:58 ` Vladimir Davydov
2015-01-07 14:38   ` Michal Hocko
2015-01-08  8:33     ` Vladimir Davydov
2015-01-08  9:09       ` Michal Hocko
2015-02-02  8:37 ` [LSF/MM TOPIC ATTEND] - THP benefits Vlastimil Babka

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=20150106161435.GF20860@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /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