From: Amir Goldstein <amir73il@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: "khazhy@google.com" <khazhy@google.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH RFC] nfsd: avoid recursive locking through fsnotify
Date: Wed, 23 Mar 2022 16:00:30 +0200 [thread overview]
Message-ID: <CAOQ4uxhBH_0UqEmOdcUaV0E8oGTGF7arr+Q_EZPuQ=KWfvJWoQ@mail.gmail.com> (raw)
In-Reply-To: <20220323134851.px6s4i6iiaj4zlju@quack3.lan>
> Well, but reclaim from kswapd is always the main and preferred source of
> memory reclaim. And we will kick kswapd to do work if we are running out of
> memory. Doing direct filesystem slab reclaim from mark allocation is useful
> only to throttle possibly aggressive mark allocations to the speed of
> reclaim (instead of getting ENOMEM). So I'm still not convinced this is a
> big issue but I certainly won't stop you from implementing more fine
> grained GFP mode selection and lockdep annotations if you want to go that
> way :).
Well it was just two lines of code to annotate the fanotify mutex as its own
class, so I just did that:
https://github.com/amir73il/linux/commit/7b4b6e2c0bd1942cd130e9202c4b187a8fb468c6
Thanks,
Amir.
next prev parent reply other threads:[~2022-03-23 14:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220319001635.4097742-1-khazhy@google.com>
2022-03-19 0:36 ` Trond Myklebust
2022-03-19 1:45 ` Khazhy Kumykov
2022-03-19 9:36 ` Amir Goldstein
2022-03-21 11:23 ` Jan Kara
2022-03-21 11:56 ` Amir Goldstein
2022-03-21 14:51 ` Jan Kara
2022-03-22 22:41 ` Amir Goldstein
2022-03-23 10:41 ` Jan Kara
2022-03-23 11:40 ` Amir Goldstein
2022-03-23 13:48 ` Jan Kara
2022-03-23 14:00 ` Amir Goldstein [this message]
2022-03-23 14:28 ` Jan Kara
2022-03-23 15:46 ` Amir Goldstein
2022-03-23 19:31 ` Amir Goldstein
2022-03-24 19:17 ` Amir Goldstein
2022-03-25 9:29 ` Jan Kara
2022-03-27 18:14 ` Amir Goldstein
2022-03-21 22:50 ` Trond Myklebust
2022-03-21 23:36 ` Khazhy Kumykov
2022-03-21 23:50 ` Trond Myklebust
2022-03-22 10:37 ` Jan Kara
2022-03-21 17:06 ` Khazhy Kumykov
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='CAOQ4uxhBH_0UqEmOdcUaV0E8oGTGF7arr+Q_EZPuQ=KWfvJWoQ@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=khazhy@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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