From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCH 3/6] memcg: track shared inodes with dirty pages Date: Thu, 15 Jan 2015 14:08:40 -0500 Message-ID: <20150115190840.GD28195@htj.dyndns.org> References: <20150115180242.10450.92.stgit@buzz> <20150115184914.10450.51964.stgit@buzz> <20150115185543.GA28195@htj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Konstantin Khebnikov , "linux-mm@kvack.org" , cgroups@vger.kernel.org, Roman Gushchin , Jan Kara , Dave Chinner , Linux Kernel Mailing List , linux-fsdevel To: Konstantin Khlebnikov Return-path: Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-Id: linux-fsdevel.vger.kernel.org Hello, On Thu, Jan 15, 2015 at 11:04:49PM +0400, Konstantin Khlebnikov wrote: > I know. Absolutely accurate per-page solution looks too complicated for me. > Is there any real demand for accurate handling dirty set in shared inodes? > Doing whole accounting in per-inode basis makes life so much easier. Ah, yeah, patch #3 arrived in isolation, so I thought it was part of something completely different. I definitely thought about doing it per-inode too (and also requiring memcg to attribute pages according to its inode rather than individual pages). I'll look into the patchset and try to identify the pros and cons of our approaches. 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: email@kvack.org