From: Jan Kara <jack@suse.cz>
To: Greg Thelen <gthelen@google.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
lsf@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [Lsf] [LSF][MM] rough agenda for memcg.
Date: Thu, 31 Mar 2011 14:27:47 +0200 [thread overview]
Message-ID: <20110331122747.GC21524@quack.suse.cz> (raw)
In-Reply-To: <BANLkTikLPTr46S6k5LaZ3sfsXG=PrQNvGA@mail.gmail.com>
On Wed 30-03-11 22:52:49, Greg Thelen wrote:
> On Wed, Mar 30, 2011 at 7:01 PM, KAMEZAWA Hiroyuki
> <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > I'd like to sort out topics before going. Please fix if I don't catch enough.
> >
> > mentiont to 1. later...
> >
> > Main topics on 2. Memcg Dirty Limit and writeback ....is
> >
> > a) How to implement per-memcg dirty inode finding method (list) and
> > how flusher threads handle memcg.
>
> I have some very rough code implementing the ideas discussed in
> http://thread.gmane.org/gmane.linux.kernel.mm/59707
> Unfortunately, I do not yet have good patches, but maybe an RFC series
> soon. I can provide update on the direction I am thinking.
>
> > b) Hot to interact with IO-Less dirty page reclaim.
> > IIUC, if memcg doesn't handle this correctly, OOM happens.
>
> The last posted memcg dirty writeback patches were based on -mm at the
> time, which did not have IO-less balance_dirty_pages. I have an
> approach which I _think_ will be compatible with IO-less
> balance_dirty_pages(), but I need to talk with some writeback guys to
> confirm. Seeing the Writeback talk Mon 9:30am should be very useful
> for me.
>
> > Greg, do we need to have a shared session with I/O guys ?
> > If needed, current schedule is O.K. ?
>
> We can contact any interested writeback guys to see if they want to
> attend memcg-writeback discussion. We might be able to defer this
> detail until Mon morning.
Yes, I plan to take part in this discussion. If this would be joint
session with fs people (which kind of makes sense) it's simpler for
me but I can surely handle if it isn't :).
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-31 12:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 2:01 [LSF][MM] rough agenda for memcg KAMEZAWA Hiroyuki
2011-03-31 5:52 ` Greg Thelen
2011-03-31 12:27 ` Jan Kara [this message]
2011-03-31 6:01 ` Balbir Singh
2011-03-31 6:03 ` Ying Han
2011-03-31 9:15 ` Zhu Yanhai
2011-04-01 2:36 ` Michel Lespinasse
2011-03-31 9:23 ` [Lsf] " Pavel Emelyanov
2011-03-31 16:20 ` Andrea Arcangeli
2011-03-31 18:14 ` Ying Han
2011-03-31 19:00 ` Pavel Emelyanov
2011-03-31 19:16 ` Ying Han
2011-03-31 19:22 ` Ying Han
2011-03-31 15:59 ` Andrea Arcangeli
2011-03-31 20:06 ` Johannes Weiner
2011-04-01 3:18 ` Michel Lespinasse
2011-04-01 1:16 ` KAMEZAWA Hiroyuki
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=20110331122747.GC21524@quack.suse.cz \
--to=jack@suse.cz \
--cc=gthelen@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lsf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.