From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH 0/2 v3] xfs: improve transaction rate scalability
Date: Wed, 20 May 2020 08:23:08 +1000 [thread overview]
Message-ID: <20200519222310.2576434-1-david@fromorbit.com> (raw)
Hi folks,
This is the third version of the patchset to improve the transaction
rate on higher CPU count machines. The previous versions can be found
here:
https://lore.kernel.org/linux-xfs/20200512025949.1807131-1-david@fromorbit.com/
https://lore.kernel.org/linux-xfs/20200512092811.1846252-1-david@fromorbit.com/
Changes for v3 are:
- completely reorganise the struct xfs_mount, not just a subset of
the variables. This seems to improve performance even more than
the original version. (Christoph requested this.)
- remove the m_active_trans counter rather than convert it to percpu
as Darrick suggested.
Results are just as good or better than previous versions, passes
fstests without regressions on both low PCU count and high CPU count
test VMs.
Cheers,
Dave.
next reply other threads:[~2020-05-19 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 22:23 Dave Chinner [this message]
2020-05-19 22:23 ` [PATCH 1/2] xfs: separate read-only variables in struct xfs_mount Dave Chinner
2020-05-20 6:57 ` Christoph Hellwig
2020-05-20 7:12 ` Dave Chinner
2020-05-20 9:43 ` Chaitanya Kulkarni
2020-05-20 20:44 ` Darrick J. Wong
2020-05-19 22:23 ` [PATCH 2/2] xfs: remove the m_active_trans counter Dave Chinner
2020-05-20 7:01 ` Christoph Hellwig
2020-05-20 7:13 ` Dave Chinner
2020-05-20 7:17 ` Christoph Hellwig
2020-05-20 20:47 ` Darrick J. Wong
2020-05-20 21:51 ` Dave Chinner
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=20200519222310.2576434-1-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
/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