From: Mikhail Rudenko <xyzzy@yandex-team.ru>
To: Jan Kara <jack@suse.cz>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] Defer final iputs for dirty-time inodes in PF_MEMALLOC context
Date: Tue, 01 Sep 2026 15:54:59 +0300 [thread overview]
Message-ID: <86zey1qg7k.fsf@yandex-team.ru> (raw)
In-Reply-To: <27v2ckdgybmvxog5b55sr3o6ri4bkbzu6ycwtjwckrhzyazxzd@7qruolrsu5t7>
Hi Jan,
On 2026-09-01 at 14:24 +02, Jan Kara <jack@suse.cz> wrote:
> Thanks for your patches. I've actually submitted patches to address this
> problem back at the end of April [1]. In particularly the problem you
> report was addressed somewhat differently by patch 1. We've then discussed
> them at LSF/MM/BPF summit and people mostly agreed with the approach, just
> there were some requests for better parallelization of deferred inode
> reclaim (which I so far failed to implement). But it's currently high on my
> todo list so I should hopefully send v2 of the patches for the next merge
> window.
>
> Honza
>
> [1] https://lore.kernel.org/all/20260429174850.18223-1-jack@suse.cz/
My bad, should've done better prior art reasearch. :) Looking forward
to your v2 then.
--
Best regards,
Mikhail Rudenko
prev parent reply other threads:[~2026-09-01 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 9:43 [PATCH RFC 0/2] Defer final iputs for dirty-time inodes in PF_MEMALLOC context Mikhail Rudenko
2026-08-13 9:43 ` [PATCH RFC 1/2] fs: add superblock deferred iput infrastructure Mikhail Rudenko
2026-08-13 9:43 ` [PATCH RFC 2/2] fs: defer dirtytime iput from PF_MEMALLOC context Mikhail Rudenko
2026-09-01 10:10 ` [PATCH RFC 0/2] Defer final iputs for dirty-time inodes in " Mikhail Rudenko
2026-09-01 12:24 ` Jan Kara
2026-09-01 12:54 ` Mikhail Rudenko [this message]
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=86zey1qg7k.fsf@yandex-team.ru \
--to=xyzzy@yandex-team.ru \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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