From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vivek Goyal Subject: Re: [Lsf] IO less throttling and cgroup aware writeback (Was: Re: Preliminary Agenda and Activities for LSF) Date: Wed, 6 Apr 2011 11:39:54 -0400 Message-ID: <20110406153954.GB18777@redhat.com> References: <20110330153757.GD1291@redhat.com> <20110330222002.GB20849@dastard> <20110331141637.GA11139@redhat.com> <20110331222756.GC2904@dastard> <20110401171838.GD20986@redhat.com> <20110401214947.GE6957@dastard> <20110405131359.GA14239@redhat.com> <20110405225639.GB31057@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dave Chinner , Greg Thelen , James Bottomley , lsf@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org To: Curt Wohlgemuth Return-path: Received: from mx1.redhat.com ([209.132.183.28]:7656 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932101Ab1DFPkb (ORCPT ); Wed, 6 Apr 2011 11:40:31 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Apr 06, 2011 at 07:49:25AM -0700, Curt Wohlgemuth wrote: [..] > > Can someone describe a valid shared inode use case? If not, we > > should not even consider it as a requirement and explicitly document > > it as a "not supported" use case. > > At the very least, when a task is moved from one cgroup to another, > we've got a shared inode case. This probably won't happen more than > once for most tasks, but it will likely be common. I am hoping that for such cases sooner or later inode movement will automatically take place. At some point of time, inode will be clean and no more on memcg_bdi list. And when it is dirtied again, I am hoping it will be queued on new groups's list and not on old group's list? Greg? Thanks Vivek