linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	linux-mm@kvack.org, cgroups@vger.kernel.org,
	linux-kernel@vger.kernel.org, Ying Han <yinghan@google.com>,
	Hugh Dickins <hughd@google.com>,
	Glauber Costa <glommer@parallels.com>,
	Michel Lespinasse <walken@google.com>,
	Greg Thelen <gthelen@google.com>,
	Balbir Singh <bsingharora@gmail.com>
Subject: Re: [patch -v4 4/8] memcg: enhance memcg iterator to support predicates
Date: Wed, 5 Jun 2013 01:58:49 -0700	[thread overview]
Message-ID: <20130605085849.GB7990@mtj.dyndns.org> (raw)
In-Reply-To: <20130605085239.GF15997@dhcp22.suse.cz>

Hey, Michal.

On Wed, Jun 05, 2013 at 10:52:39AM +0200, Michal Hocko wrote:
> > One of the core jobs of being a maintainer is ensuring the code stays
> > in readable and maintainable state.
> 
> As you might know I am playing the maintainer role for around year and a
> half and there were many improvemtns merged since then (and some faults
> as well of course).
> There is a lot of space for improvements and I work at areas as time
> permits focusing more at reviews for other people are willing to do.

I see.  Yeah, maybe I was attributing too many things to you.  Sorry
about that.

> [...]
> 
> Please stop distracting from the main purpose of this discussion with
> side tracks and personal things.

I'm not really trying to distract you.  I suppose my points are.

* Let's please pay more attention to each change which goes in.

* Let's prioritize cleanups over new features because, whatever the
  history, memcg needs quite some cleanups.

I really don't have personal vandetta against you.  I'm mostly just
very frustrated about memcg.  Maybe you're too.

Anyways, so you aren't gonna try the skipping thing?

Thanks.

-- 
tejun

--
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-06-05  8:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 10:18 [patch v4] Soft limit rework Michal Hocko
2013-06-03 10:18 ` [patch -v4 1/8] memcg: integrate soft reclaim tighter with zone shrinking code Michal Hocko
2013-06-03 10:18 ` [patch -v4 2/8] memcg: Get rid of soft-limit tree infrastructure Michal Hocko
2013-06-03 10:18 ` [patch -v4 3/8] vmscan, memcg: Do softlimit reclaim also for targeted reclaim Michal Hocko
2013-06-03 10:18 ` [patch -v4 4/8] memcg: enhance memcg iterator to support predicates Michal Hocko
2013-06-04  1:07   ` Tejun Heo
2013-06-04 13:45     ` Michal Hocko
2013-06-04 19:36       ` Tejun Heo
2013-06-04 20:48         ` Michal Hocko
2013-06-04 20:54           ` Tejun Heo
2013-06-05  7:37             ` Michal Hocko
2013-06-05  8:05               ` Tejun Heo
2013-06-05  8:52                 ` Michal Hocko
2013-06-05  8:58                   ` Tejun Heo [this message]
2013-06-05  9:07                     ` Michal Hocko
2013-06-05  9:09                       ` Tejun Heo
2013-06-07  0:48                         ` Tejun Heo
2013-06-07  8:25                           ` Michal Hocko
2013-06-10  7:48   ` Michal Hocko
2013-06-03 10:18 ` [patch -v4 5/8] memcg: track children in soft limit excess to improve soft limit Michal Hocko
2013-06-03 10:18 ` [patch -v4 6/8] memcg, vmscan: Do not attempt soft limit reclaim if it would not scan anything Michal Hocko
2013-06-03 10:18 ` [patch -v4 7/8] memcg: Track all children over limit in the root Michal Hocko
2013-06-03 10:18 ` [patch -v4 8/8] memcg, vmscan: do not fall into reclaim-all pass too quickly Michal Hocko
2013-06-04 16:27 ` [patch v4] Soft limit rework Balbir Singh
2013-06-04 16:38   ` Michal Hocko
2013-06-04 17:57     ` Balbir Singh
2013-06-04 18:08       ` Michal Hocko
2013-06-11 15:43 ` Michal Hocko
2013-06-17 14:01   ` Michal Hocko

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=20130605085849.GB7990@mtj.dyndns.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bsingharora@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=glommer@parallels.com \
    --cc=gthelen@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=walken@google.com \
    --cc=yinghan@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;
as well as URLs for NNTP newsgroup(s).