cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 13/13] GFS2: Optimization of GL_ST_UNLOCK state
Date: Mon, 19 Nov 2018 07:29:31 -0600	[thread overview]
Message-ID: <20181119132931.15726-14-rpeterso@redhat.com> (raw)
In-Reply-To: <20181119132931.15726-1-rpeterso@redhat.com>

The previous patch added a new GL_ST_UNLOCK state that simply
cleared the GLF_LOCK bit, then went into the RUN state. Since the
RUN state immediately sets the GLF_LOCK again and does a few other
things, we can optimize it by putting GL_ST_UNLOCK in the middle
of the GL_ST_RUN state. This avoids unlock-then-lock and extra
checks and skips directly to the resulting promotion/demotion state.

Signed-off-by: Bob Peterson <rpeterso@redhat.com>
---
 fs/gfs2/glock.c | 6 ++----
 fs/gfs2/glock.h | 2 +-
 2 files changed, 3 insertions(+), 5 deletions(-)

diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
index 33f4a530caf4..29e6d9a440ec 100644
--- a/fs/gfs2/glock.c
+++ b/fs/gfs2/glock.c
@@ -724,7 +724,9 @@ static void __state_machine(struct gfs2_glock *gl, int new_state,
 
 			GLOCK_BUG_ON(gl, test_bit(GLF_DEMOTE_IN_PROGRESS,
 						  &gl->gl_flags));
+			/* Fall through */
 
+		case GL_ST_UNLOCK:
 			if (test_bit(GLF_DEMOTE, &gl->gl_flags) &&
 			    gl->gl_demote_state != gl->gl_state)
 				gl->gl_mch = nonblock ? GL_ST_DEMOTE_NONBLOCK :
@@ -751,10 +753,6 @@ static void __state_machine(struct gfs2_glock *gl, int new_state,
 			gl->gl_mch = GL_ST_RUN;
 			break;
 
-		case GL_ST_UNLOCK:
-			clear_bit(GLF_LOCK, &gl->gl_flags);
-			gl->gl_mch = GL_ST_RUN;
-			break;
 		}
 	} while (gl->gl_mch != GL_ST_IDLE || new_state != GL_ST_IDLE);
 
diff --git a/fs/gfs2/glock.h b/fs/gfs2/glock.h
index 5bbf3118c7c3..e1a5bc2d3f76 100644
--- a/fs/gfs2/glock.h
+++ b/fs/gfs2/glock.h
@@ -131,7 +131,7 @@ enum gl_machine_states {
 	GL_ST_PROMOTE = 6,	   /* Promote the lock */
 	GL_ST_RUN = 7,		/* "Run" or progress the lock */
 	GL_ST_WORK = 8,		/* Perform general glock work */
-	GL_ST_UNLOCK = 9,	/* Unlock then run */
+	GL_ST_UNLOCK = 9,	/* Unlock the glock */
 };
 
 struct lm_lockops {
-- 
2.19.1



      parent reply	other threads:[~2018-11-19 13:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 13:29 [Cluster-devel] [PATCH 00/13] Radical Reform of glock state machine (take 2) Bob Peterson
2018-11-19 13:29 ` [Cluster-devel] [PATCH 01/13] GFS2: Remove gotos from function run_queue Bob Peterson
2018-11-19 13:29 ` [Cluster-devel] [PATCH 02/13] GFS2: Make do_xmote determine its own gh parameter Bob Peterson
2018-11-19 14:00   ` Steven Whitehouse
2018-11-19 21:06     ` Bob Peterson
2018-11-20 15:46       ` Steven Whitehouse
2018-11-19 13:29 ` [Cluster-devel] [PATCH 03/13] GFS2: Eliminate a goto in finish_xmote Bob Peterson
2018-11-19 13:49   ` Steven Whitehouse
2018-11-19 21:26     ` Bob Peterson
2018-11-20 15:52       ` Steven Whitehouse
2018-11-19 13:29 ` [Cluster-devel] [PATCH 04/13] GFS2: Baby step toward a real state machine: finish_xmote Bob Peterson
2018-11-19 13:29 ` [Cluster-devel] [PATCH 05/13] GFS2: Add do_xmote states to state machine Bob Peterson
2018-11-19 13:29 ` [Cluster-devel] [PATCH 06/13] GFS2: Make do_xmote not call the state machine again Bob Peterson
2018-11-19 13:29 ` [Cluster-devel] [PATCH 07/13] GFS2: Add blocking and non-blocking demote to state machine Bob Peterson
2018-11-19 13:29 ` [Cluster-devel] [PATCH 08/13] GFS2: Add a new GL_ST_PROMOTE state to glock " Bob Peterson
2018-11-19 13:29 ` [Cluster-devel] [PATCH 09/13] GFS2: Replace run_queue with new GL_ST_RUN state in " Bob Peterson
2018-11-19 13:29 ` [Cluster-devel] [PATCH 10/13] GFS2: Reduce redundancy in GL_ST_DEMOTE_NONBLOCK state Bob Peterson
2018-11-19 13:29 ` [Cluster-devel] [PATCH 11/13] GFS2: Reduce glock_work_func to a single call to state_machine Bob Peterson
2018-11-19 13:29 ` [Cluster-devel] [PATCH 12/13] GFS2: Add new GL_ST_UNLOCK state to reduce calls to the __ version Bob Peterson
2018-11-19 13:29 ` Bob Peterson [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=20181119132931.15726-14-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).