On 25.06.21 17:55, Michal Koutný wrote:
Is it possible to prevent inode/dentry trashing for example by limiting the cache per process(-group)?Yes. Unless you have disabled it with CONFIG_MEMCG_KMEM or cgroup.memory=nokmem, dentries and inodes are charged to respective cgroups. And you can limit overall memory of a cgroup, see memory.{max,high} attributes. (You suggest this inode/dentry consumption is dominant enough to affect other jobs, so the limit would keep it constrained as you intend).
Could you please tell a bit more how this really works ? (maybe some pointers to the code) I'm curios what happens if those cache objects are used by different cgroups - are they accounted to multiple times (once per cgroup) ? What happens when one cgroup using some cache object reaching its limit, wile another one does not ? --mtx -- --- Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren GPG/PGP-Schlüssel zu. --- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info@xxxxxxxxx -- +49-151-27565287
