From: "Theodore Ts'o" <tytso@mit.edu>
To: Xing Zhengjun <zhengjun.xing@linux.intel.com>
Cc: Jan Kara <jack@suse.cz>,
kernel test robot <oliver.sang@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com
Subject: Re: [LKP] [ext4] 05c2c00f37: aim7.jobs-per-min -11.8% regression
Date: Fri, 3 Sep 2021 08:32:21 -0400 [thread overview]
Message-ID: <YTIV1SozOGwT/DQw@mit.edu> (raw)
In-Reply-To: <8ac28fce-0cfb-cc4d-1a3d-2f104ff46767@linux.intel.com>
On Fri, Sep 03, 2021 at 01:28:25PM +0800, Xing Zhengjun wrote:
> Hi Jan,
>
> Do you have time to look at this? I re-test it in v5.13 and v5.14, the
> regression still existed. Thanks.
> > So as we chatted on today's call probably the best option is to leave the
> > code as is for now and instead work on moving away from orphan list
> > altogether. I'll revive my patches to do that.
The orphan_file feature has landed in for the 5.15 merge window. When
enabled, it provides multiple blocks to store the set of orphaned
inodes, which provides parallelism for parallel truncate and unlink
operations.
It requires a development version of e2fsprogs to use, and so the
zero-day bot won't be able to test it for a little while.
Cheers,
- Ted
prev parent reply other threads:[~2021-09-03 12:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 12:08 [ext4] 05c2c00f37: aim7.jobs-per-min -11.8% regression kernel test robot
[not found] ` <a8947cee-11f5-8d59-a3ff-1c516276592e@linux.intel.com>
2021-05-20 9:51 ` [LKP] " Jan Kara
2021-05-21 1:16 ` Xing Zhengjun
2021-05-21 9:27 ` Jan Kara
2021-05-21 16:42 ` Theodore Y. Ts'o
2021-05-25 9:22 ` Jan Kara
2021-05-25 17:15 ` Theodore Ts'o
2021-05-31 16:57 ` Jan Kara
2021-06-03 16:10 ` Jan Kara
2021-09-03 5:28 ` Xing Zhengjun
2021-09-03 12:32 ` Theodore Ts'o [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=YTIV1SozOGwT/DQw@mit.edu \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=zhengjun.xing@linux.intel.com \
/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