From: Li Zefan <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>,
LKML <linux-kernel@vger.kernel.org>,
cgroups <cgroups@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v6 0/5] memcg, cgroup: kill css id
Date: Tue, 24 Sep 2013 08:32:03 +0800 [thread overview]
Message-ID: <5240DD83.1070509@huawei.com> (raw)
In-Reply-To: <20130923131215.GI30946@htj.dyndns.org>
On 2013/9/23 21:12, Tejun Heo wrote:
> On Mon, Sep 23, 2013 at 09:08:16AM -0400, Tejun Heo wrote:
>> Hello,
>>
>> On Mon, Sep 23, 2013 at 04:55:20PM +0800, Li Zefan wrote:
>>> The whole patchset has been acked and reviewed by Michal and Tejun.
>>> Could you merge it into mm tree?
>>
>> Ah... I really hoped that this had been merged during -rc1 window.
>> Andrew, would it be okay to carry this series through cgroup tree? It
>> doesn't really have much to do with mm proper and it's a PITA to have
>> to keep updating css_id code from cgroup side when it's scheduled to
>> go away. If carried in -mm, it's likely to cause conflicts with
>> ongoing cgroup changes too.
I would love to see this patchset go through cgroup tree. The changes to
memcg is quite small, and as -mm tree is based on -next it won't cause
future conflicts.
>
> Also, wasn't this already in -mm during the last devel cycle? ISTR
> conflicts with it in -mm with other cgroup core changes. Is there any
> specific reason why this wasn't merged during the merge windw?
>
No, it never went into -mm tree... I guess it's because Andrew was too
busy and overlooked this patchset?
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Li Zefan <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>,
LKML <linux-kernel@vger.kernel.org>,
cgroups <cgroups@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v6 0/5] memcg, cgroup: kill css id
Date: Tue, 24 Sep 2013 08:32:03 +0800 [thread overview]
Message-ID: <5240DD83.1070509@huawei.com> (raw)
In-Reply-To: <20130923131215.GI30946@htj.dyndns.org>
On 2013/9/23 21:12, Tejun Heo wrote:
> On Mon, Sep 23, 2013 at 09:08:16AM -0400, Tejun Heo wrote:
>> Hello,
>>
>> On Mon, Sep 23, 2013 at 04:55:20PM +0800, Li Zefan wrote:
>>> The whole patchset has been acked and reviewed by Michal and Tejun.
>>> Could you merge it into mm tree?
>>
>> Ah... I really hoped that this had been merged during -rc1 window.
>> Andrew, would it be okay to carry this series through cgroup tree? It
>> doesn't really have much to do with mm proper and it's a PITA to have
>> to keep updating css_id code from cgroup side when it's scheduled to
>> go away. If carried in -mm, it's likely to cause conflicts with
>> ongoing cgroup changes too.
I would love to see this patchset go through cgroup tree. The changes to
memcg is quite small, and as -mm tree is based on -next it won't cause
future conflicts.
>
> Also, wasn't this already in -mm during the last devel cycle? ISTR
> conflicts with it in -mm with other cgroup core changes. Is there any
> specific reason why this wasn't merged during the merge windw?
>
No, it never went into -mm tree... I guess it's because Andrew was too
busy and overlooked this patchset?
next prev parent reply other threads:[~2013-09-24 0:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 8:55 [PATCH v6 0/5] memcg, cgroup: kill css id Li Zefan
2013-09-23 8:55 ` Li Zefan
2013-09-23 8:55 ` [PATCH v6 1/5] memcg: convert to use cgroup_is_descendant() Li Zefan
2013-09-23 8:55 ` Li Zefan
2013-09-23 8:56 ` [PATCH v6 2/5] memcg: convert to use cgroup id Li Zefan
2013-09-23 8:56 ` Li Zefan
[not found] ` <524001F8.6070205-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-09-23 8:56 ` [PATCH v6 3/5] memcg: fail to create cgroup if the cgroup id is too big Li Zefan
2013-09-23 8:56 ` Li Zefan
2013-09-23 8:56 ` Li Zefan
2013-09-23 8:56 ` [PATCH v6 4/5] memcg: stop using css id Li Zefan
2013-09-23 8:56 ` Li Zefan
2013-09-23 8:56 ` Li Zefan
2013-09-23 8:57 ` [PATCH v6 5/5] cgroup: kill css_id Li Zefan
2013-09-23 8:57 ` Li Zefan
2013-09-23 8:57 ` Li Zefan
2013-09-23 13:08 ` [PATCH v6 0/5] memcg, cgroup: kill css id Tejun Heo
2013-09-23 13:08 ` Tejun Heo
2013-09-23 13:08 ` Tejun Heo
[not found] ` <20130923130816.GH30946-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-09-23 13:12 ` Tejun Heo
2013-09-23 13:12 ` Tejun Heo
2013-09-23 13:12 ` Tejun Heo
2013-09-24 0:32 ` Li Zefan [this message]
2013-09-24 0:32 ` Li Zefan
[not found] ` <5240DD83.1070509-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-09-24 0:52 ` Andrew Morton
2013-09-24 0:52 ` Andrew Morton
2013-09-24 0:52 ` Andrew Morton
2013-09-24 1:30 ` Tejun Heo
2013-09-24 1:30 ` Tejun Heo
2013-09-24 1:52 ` Tejun Heo
2013-09-24 1:52 ` Tejun Heo
[not found] ` <20130924015211.GD3482-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-09-24 1:54 ` Stephen Rothwell
2013-09-24 1:54 ` Stephen Rothwell
2013-09-24 1:46 ` Tejun Heo
2013-09-24 1:46 ` Tejun Heo
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=5240DD83.1070509@huawei.com \
--to=lizefan@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=tj@kernel.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.