From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753861Ab3LQMsQ (ORCPT ); Tue, 17 Dec 2013 07:48:16 -0500 Received: from cantor2.suse.de ([195.135.220.15]:54567 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753786Ab3LQMsJ (ORCPT ); Tue, 17 Dec 2013 07:48:09 -0500 Date: Tue, 17 Dec 2013 13:48:07 +0100 From: Michal Hocko To: Li Zefan Cc: Hugh Dickins , Tejun Heo , Johannes Weiner , Andrew Morton , KAMEZAWA Hiroyuki , linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: 3.13-rc breaks MEMCG_SWAP Message-ID: <20131217124807.GB28991@dhcp22.suse.cz> References: <52AEC989.4080509@huawei.com> <20131216095345.GB23582@dhcp22.suse.cz> <20131216104042.GC23582@dhcp22.suse.cz> <20131216163530.GH32509@htj.dyndns.org> <20131216171937.GG26797@dhcp22.suse.cz> <20131216172143.GJ32509@htj.dyndns.org> <52AFC163.5010507@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52AFC163.5010507@huawei.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 17-12-13 11:13:39, Li Zefan wrote: > On 2013/12/17 9:41, Hugh Dickins wrote: > > On Mon, 16 Dec 2013, Tejun Heo wrote: > >> On Mon, Dec 16, 2013 at 06:19:37PM +0100, Michal Hocko wrote: > >>> I have to think about it some more (the brain is not working anymore > >>> today). But what we really need is that nobody gets the same id while > >>> the css is alive. > > That's what I meant to do in my last reply. > > But I'm confused by > > "How would this work? .. the swap will be there > after the last reference to css as well." Sorry about the confusion. Johannes correctly pointed out that a css reference is taken when we record memcg id and released after the record is removed. -- Michal Hocko SUSE Labs From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Hocko Subject: Re: 3.13-rc breaks MEMCG_SWAP Date: Tue, 17 Dec 2013 13:48:07 +0100 Message-ID: <20131217124807.GB28991@dhcp22.suse.cz> References: <52AEC989.4080509@huawei.com> <20131216095345.GB23582@dhcp22.suse.cz> <20131216104042.GC23582@dhcp22.suse.cz> <20131216163530.GH32509@htj.dyndns.org> <20131216171937.GG26797@dhcp22.suse.cz> <20131216172143.GJ32509@htj.dyndns.org> <52AFC163.5010507@huawei.com> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <52AFC163.5010507@huawei.com> Sender: owner-linux-mm@kvack.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Li Zefan Cc: Hugh Dickins , Tejun Heo , Johannes Weiner , Andrew Morton , KAMEZAWA Hiroyuki , linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org On Tue 17-12-13 11:13:39, Li Zefan wrote: > On 2013/12/17 9:41, Hugh Dickins wrote: > > On Mon, 16 Dec 2013, Tejun Heo wrote: > >> On Mon, Dec 16, 2013 at 06:19:37PM +0100, Michal Hocko wrote: > >>> I have to think about it some more (the brain is not working anymore > >>> today). But what we really need is that nobody gets the same id while > >>> the css is alive. > > That's what I meant to do in my last reply. > > But I'm confused by > > "How would this work? .. the swap will be there > after the last reference to css as well." Sorry about the confusion. Johannes correctly pointed out that a css reference is taken when we record memcg id and released after the record is removed. -- 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: email@kvack.org