From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 0/2] GFS2: Bulk submit ordered writes
Date: Mon, 14 May 2018 09:18:55 -0500 [thread overview]
Message-ID: <20180514141857.27461-1-rpeterso@redhat.com> (raw)
This patch set is designed to submit the ordered writes list in bulk.
This is a performance enhancement from the way we currently do it,
which is submit->wait->submit->wait. Submitting them in bulk takes
better advantage of the io elevator and vfs below us.
The first patch merely moves function gfs2_ordered_wait. The second
patch implements the actual change.
Bob Peterson (2):
GFS2: Move function gfs2_ordered_wait before ordered_write
GFS2: Submit all ordered writes in bulk, wait after that
fs/gfs2/log.c | 48 +++++++++++++++++++++++++++++++-----------------
1 file changed, 31 insertions(+), 17 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-14 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 14:18 Bob Peterson [this message]
2018-05-14 14:18 ` [Cluster-devel] [GFS2 PATCH 1/2] GFS2: Move function gfs2_ordered_wait before ordered_write Bob Peterson
2018-05-14 14:18 ` [Cluster-devel] [GFS2 PATCH 2/2] GFS2: Submit all ordered writes in bulk, wait after that Bob Peterson
2018-05-15 20:31 ` Andreas Gruenbacher
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=20180514141857.27461-1-rpeterso@redhat.com \
--to=rpeterso@redhat.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).