From: Dave Chinner <david@fromorbit.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org, lkp@lists.01.org, lkp@intel.com,
ying.huang@intel.com, feng.tang@intel.com,
zhengjun.xing@linux.intel.com, fengwei.yin@intel.com
Subject: Re: [xfs] 345a4666a7: vm-scalability.throughput -91.7% regression
Date: Fri, 22 Jul 2022 07:33:37 +1000 [thread overview]
Message-ID: <20220721213337.GV3861211@dread.disaster.area> (raw)
In-Reply-To: <Ytlr9vZbF4SOfA2n@xsang-OptiPlex-9020>
On Thu, Jul 21, 2022 at 11:08:38PM +0800, kernel test robot wrote:
>
> (just FYI for the possible performance impact of disabling large folios,
> our config, as attached, set default N to XFS_LARGE_FOLIOS)
>
>
> Greeting,
>
> FYI, we noticed a -91.7% regression of vm-scalability.throughput due to commit:
>
>
> commit: 345a4666a721a81c343186768cdd95817767195f ("xfs: disable large folios except for developers")
Say what? I've never seen that change go past on a public list...
> https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git xfs-5.20-merge
Oh, it's in a developer's working tree, not something that has been
proposed for review let alone been merged.
So why is this report being sent to lkml, linux-xfs, etc as if it
was a change merged into an upstream tree rather than just the
developer who owns the tree the commit is in?
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-07-21 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 15:08 [xfs] 345a4666a7: vm-scalability.throughput -91.7% regression kernel test robot
2022-07-21 21:33 ` Dave Chinner [this message]
2022-07-21 21:38 ` Darrick J. Wong
2022-07-22 2:10 ` Oliver Sang
2022-07-22 2:21 ` Darrick J. Wong
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=20220721213337.GV3861211@dread.disaster.area \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=djwong@kernel.org \
--cc=feng.tang@intel.com \
--cc=fengwei.yin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=ying.huang@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