| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20150115190840.GD28195@htj.dyndns.org> Date: Thu, 15 Jan 2015 14:08:40 -0500 From: Tejun Heo <tj@...nel.org> To: Konstantin Khlebnikov <koct9i@...il.com> Cc: Konstantin Khebnikov <khlebnikov@...dex-team.ru>, "linux-mm@...ck.org" <linux-mm@...ck.org>, cgroups@...r.kernel.org, Roman Gushchin <klamm@...dex-team.ru>, Jan Kara <jack@...e.cz>, Dave Chinner <david@...morbit.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org> Subject: Re: [PATCH 3/6] memcg: track shared inodes with dirty pages 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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists