From: Christoph Hellwig <hch@infradead.org>
To: Zqiang <qiang.zhang1211@gmail.com>
Cc: willy@infradead.org, hch@infradead.org,
akpm@linux-foundation.org, sunhao.th@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: inode: use queue_rcu_work() instead of call_rcu()
Date: Fri, 15 Oct 2021 01:04:07 -0700 [thread overview]
Message-ID: <YWk195naAMYhh3EV@infradead.org> (raw)
In-Reply-To: <20211015080216.4871-1-qiang.zhang1211@gmail.com>
NAK.
1. We need to sort ounderlying issue first as I already said _twice_.
2. this has a major penality on all file systems
next prev parent reply other threads:[~2021-10-15 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 8:02 [PATCH] fs: inode: use queue_rcu_work() instead of call_rcu() Zqiang
2021-10-15 8:04 ` Christoph Hellwig [this message]
2021-10-15 8:28 ` Zqiang
2021-10-15 13:24 ` Christoph Hellwig
2021-10-15 13:50 ` kernel test robot
2021-10-15 13:54 ` kernel test robot
2021-10-18 2:02 ` Zqiang
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=YWk195naAMYhh3EV@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=sunhao.th@gmail.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).