linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sha Zhengju <handai.szj@gmail.com>
To: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Cc: Glauber Costa <glommer@parallels.com>
Subject: [LSF/MM TOPIC] [ATTEND] memcg page stat accounting and drop_caches
Date: Wed, 6 Feb 2013 23:08:09 +0800	[thread overview]
Message-ID: <CAFj3OHW=-WJegSvDG+Drb5p5kKX2s+F-irx07DxZEqH5_4Cxng@mail.gmail.com> (raw)

Hi,

Recently I've been working on memcg related issues based on our
production environment and requirements, and as the 2013 LSF/MM is
coming, I'd like to discuss the following topics:

- memcg page stat stuffs
This is basically from my recent works of memcg dirty/writeback page
stat accounting(https://lkml.org/lkml/2012/12/25/95). But before them
to be ready, we'd better do some optimization toward the overhead of
accounting(my idea now is mainly on root memcg, and the first attempt
is posted in the 6/8 of the aboving patchset). Another related prepare
issue is memcg page stat lock, which is found to be too large and has
nesting problem. I'm also trying to simply it and has sent out the
proposal( http://www.spinics.net/lists/linux-mm/msg50037.html), but
now it seems that there is still other race problems. Maybe I can seek
some suggestions here.

- memcg drop_caches
There are some needs of drop_caches using in memcg or in containers
like lxc, but such interface is not available now. Another control
file 'force_empty' has some function of "drop caches and anon pages",
but it's provided to make cgroup's memory usage empty and can be used
only when the cgroup has no tasks, so it make sense to implement it.
But as to the implementation, drop_caches needs to handle both page
caches and dentry/inode caches. After a rough investigation, I think
memcg slab/slub shrinker is in the preparation stage after Glauber's
kmem infrastructure (I'm also interested and expecting his following
work about memcg shrinker mentioned in his LSF/MM proposals. : ) ) ,
and for page caches we may do some generalisation to the existing
'force_empty' interface.



Thanks,
Sha

--
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:[~2013-02-06 15:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAFj3OHW=-WJegSvDG+Drb5p5kKX2s+F-irx07DxZEqH5_4Cxng@mail.gmail.com' \
    --to=handai.szj@gmail.com \
    --cc=glommer@parallels.com \
    --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