From: Yin Fengwei <fengwei.yin@intel.com>
To: Yujie Liu <yujie.liu@intel.com>, Jan Kara <jack@suse.cz>
Cc: Oliver Sang <oliver.sang@intel.com>, <oe-lkp@lists.linux.dev>,
<lkp@intel.com>, <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Guo Xuenan <guoxuenan@huawei.com>,
<linux-fsdevel@vger.kernel.org>, <ying.huang@intel.com>,
<feng.tang@intel.com>
Subject: Re: [linus:master] [readahead] ab4443fe3c: vm-scalability.throughput -21.4% regression
Date: Wed, 6 Mar 2024 13:36:16 +0800 [thread overview]
Message-ID: <707e218d-e9d7-4f37-b9a1-48b237e72e42@intel.com> (raw)
In-Reply-To: <dee823ca-7100-4289-8670-95047463c09d@intel.com>
On 3/4/24 13:35, Yin, Fengwei wrote:
> Even the file read throughput is almost same. But the distribution of
> order looks like a regression with ab4443fe3ca6 (more smaller order
> page cache is generated than parent commit). Thanks.
There may be confusion here. Let me clarify it as:
I shouldn't say folio order distribution is a regression. It's smaller
folio order cause more folios added in page cache for same workload. And
raise the lru lock contention which trigger the regression.
Regards
Yin, Fengwei
next prev parent reply other threads:[~2024-03-06 5:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 8:25 kernel test robot
2024-02-21 11:14 ` Jan Kara
2024-02-22 1:32 ` Oliver Sang
2024-02-22 11:50 ` Jan Kara
2024-02-22 18:37 ` Jan Kara
2024-03-04 4:59 ` Yujie Liu
2024-03-04 5:35 ` Yin, Fengwei
2024-03-06 5:36 ` Yin Fengwei [this message]
2024-03-07 9:23 ` Jan Kara
2024-03-07 18:19 ` Matthew Wilcox
2024-03-08 8:37 ` Yujie Liu
2024-03-10 6:41 ` Yin, Fengwei
2024-03-10 6:40 ` Yin, Fengwei
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=707e218d-e9d7-4f37-b9a1-48b237e72e42@intel.com \
--to=fengwei.yin@intel.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=guoxuenan@huawei.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--cc=yujie.liu@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
Powered by JetHome