From: "Michal Koutný" <mkoutny-IBi9RG/b67k@public.gmane.org>
To: Philipp Hahn <pmhahn+lkml-isSyJ6YaLy+zQB+pC5nmwQ@public.gmane.org>
Cc: "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Prevent inode/dentry trashing?
Date: Fri, 25 Jun 2021 17:55:22 +0200 [thread overview]
Message-ID: <YNX8anv2yCnkVPXy@blackbook> (raw)
In-Reply-To: <ce330972-78e6-4347-9735-72ee7bb21ef5-isSyJ6YaLy+zQB+pC5nmwQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
Hello Phillip.
On Mon, Jun 07, 2021 at 02:39:35PM +0200, Philipp Hahn <pmhahn+lkml@pmhahn.de> wrote:
> The trashed caches affect all other processes running in parallel or the
> first processes started each morning.
>
> 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).
HTH,
Michal
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-25 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 12:39 Prevent inode/dentry trashing? Philipp Hahn
[not found] ` <ce330972-78e6-4347-9735-72ee7bb21ef5-isSyJ6YaLy+zQB+pC5nmwQ@public.gmane.org>
2021-06-25 15:55 ` Michal Koutný [this message]
2021-06-28 9:40 ` Enrico Weigelt, metux IT consult
[not found] ` <88451906-e537-0ac3-b8f2-16bfc4d77ea6-EcKl7qYKIbxeoWH0uzbU5w@public.gmane.org>
2021-06-28 13:30 ` Michal Koutný
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YNX8anv2yCnkVPXy@blackbook \
--to=mkoutny-ibi9rg/b67k@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pmhahn+lkml-isSyJ6YaLy+zQB+pC5nmwQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox