From: David Sterba <dsterba@suse.cz>
To: kernel test robot <oliver.sang@intel.com>
Cc: Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
lkp@lists.01.org, lkp@intel.com, ying.huang@intel.com,
feng.tang@intel.com, zhengjun.xing@intel.com,
linux-btrfs@vger.kernel.org
Subject: Re: [btrfs] fac2f60d5f: fsmark.files_per_sec 62.6% improvement
Date: Tue, 10 Nov 2020 15:08:37 +0100 [thread overview]
Message-ID: <20201110140837.GE6756@suse.cz> (raw)
In-Reply-To: <20201110060012.GA3197@xsang-OptiPlex-9020>
On Tue, Nov 10, 2020 at 02:00:12PM +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a 62.6% improvement of fsmark.files_per_sec due to commit:
>
>
> commit: fac2f60d5fe83fd45ee08a85c2eb7a09659edbe3 ("btrfs: switch extent buffer tree lock to rw_semaphore")
Thanks for the report, that's a significant improvement, confirming the
trend that switching the locks does not regress. I've skimmed other
collected stats and it seems like an overall improvement, so the effects
should be noticeable for other metadata-heavy workloads too.
prev parent reply other threads:[~2020-11-10 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 6:00 [btrfs] fac2f60d5f: fsmark.files_per_sec 62.6% improvement kernel test robot
2020-11-10 14:08 ` 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=20201110140837.GE6756@suse.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=feng.tang@intel.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=ying.huang@intel.com \
--cc=zhengjun.xing@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;
as well as URLs for NNTP newsgroup(s).