From: David Sterba <dsterba@suse.cz>
To: kernel test robot <oliver.sang@intel.com>
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@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: [btrfs] 638ab1768a: aim7.jobs-per-min 6.2% improvement
Date: Thu, 7 Jul 2022 16:40:15 +0200 [thread overview]
Message-ID: <20220707144015.GD15169@suse.cz> (raw)
In-Reply-To: <YsGZXV7qW6bedSlc@xsang-OptiPlex-9020>
On Sun, Jul 03, 2022 at 09:27:57PM +0800, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed a 6.2% improvement of aim7.jobs-per-min due to commit:
>
>
> commit: 638ab1768a6abb9b1280783e93a3de9a95f23af8 ("btrfs: remove redundant check in up check_setget_bounds")
> https://github.com/kdave/btrfs-devel.git dev/send-v2-my-wip
Though it's on some development branch, the patch has been added to
misc-next as well and the perf improvement is on par with the estimate
5% for metadata heavy workloads. Thanks.
prev parent reply other threads:[~2022-07-07 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 13:27 [btrfs] 638ab1768a: aim7.jobs-per-min 6.2% improvement kernel test robot
2022-07-07 14:40 ` David Sterba [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=20220707144015.GD15169@suse.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=feng.tang@intel.com \
--cc=fengwei.yin@intel.com \
--cc=linux-btrfs@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