On Thu, Jan 15, 2015 at 9:55 PM, Tejun Heo <tj@xxxxxxxxxx> wrote: > On Thu, Jan 15, 2015 at 09:49:14PM +0300, Konstantin Khebnikov wrote: >> From: Konstantin Khlebnikov <khlebnikov@xxxxxxxxxxxxxx> >> >> Inode is owned only by one memory cgroup, but if it's shared it might >> contain pages from multiple cgroups. This patch detects this situation >> in memory reclaiemer and marks dirty inode with flag I_DIRTY_SHARED >> which is cleared only when data is completely written. Memcg writeback >> always writes such inodes. >> >> Signed-off-by: Konstantin Khlebnikov <khlebnikov@xxxxxxxxxxxxxx> > > This conflicts with the writeback cgroup support patchset which will > solve the writeback and memcg problem a lot more comprehensively. > > http://lkml.kernel.org/g/1420579582-8516-1-git-send-email-tj@xxxxxxxxxx > > Thanks. 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. > > -- > tejun -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
