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 4/9] gfs2: Don't pack struct lm_lockname
Date: Wed,  3 May 2017 08:46:03 -0500	[thread overview]
Message-ID: <20170503134608.31492-5-rpeterso@redhat.com> (raw)
In-Reply-To: <20170503134608.31492-1-rpeterso@redhat.com>

From: Andreas Gruenbacher <agruenba@redhat.com>

As per a suggestion by Linus, don't pack struct lm_lockname: we did that
because the struct is used as a rhashtable key, but packing tells the
compiler that the 64-bit fields in the struct may be unaligned, causing
it to generate worse code on some architectures.  Instead, rearrange the
fields in the struct so that there is no padding between fields, and
exclude any tail padding from the hash key size.

Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
---
 fs/gfs2/glock.c  | 2 +-
 fs/gfs2/incore.h | 8 ++++++--
 2 files changed, 7 insertions(+), 3 deletions(-)

diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
index b2638d8..35f3b0a 100644
--- a/fs/gfs2/glock.c
+++ b/fs/gfs2/glock.c
@@ -73,7 +73,7 @@ static DEFINE_SPINLOCK(lru_lock);
 
 static struct rhashtable_params ht_parms = {
 	.nelem_hint = GFS2_GL_HASH_SIZE * 3 / 4,
-	.key_len = sizeof(struct lm_lockname),
+	.key_len = offsetofend(struct lm_lockname, ln_type),
 	.key_offset = offsetof(struct gfs2_glock, gl_name),
 	.head_offset = offsetof(struct gfs2_glock, gl_node),
 };
diff --git a/fs/gfs2/incore.h b/fs/gfs2/incore.h
index 511e1ed..b7cf65d 100644
--- a/fs/gfs2/incore.h
+++ b/fs/gfs2/incore.h
@@ -203,11 +203,15 @@ enum {
 	DFL_DLM_RECOVERY	= 6,
 };
 
+/*
+ * We are using struct lm_lockname as an rhashtable key.  Avoid holes within
+ * the struct; padding at the end is fine.
+ */
 struct lm_lockname {
-	struct gfs2_sbd *ln_sbd;
 	u64 ln_number;
+	struct gfs2_sbd *ln_sbd;
 	unsigned int ln_type;
-} __packed __aligned(sizeof(int));
+};
 
 #define lm_name_equal(name1, name2) \
         (((name1)->ln_number == (name2)->ln_number) &&	\
-- 
2.9.3



  parent reply	other threads:[~2017-05-03 13:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 13:45 [Cluster-devel] [PATCH 0/9] GFS2: Pre-pull patch posting (merge window) Bob Peterson
2017-05-03 13:46 ` [Cluster-devel] [PATCH 1/9] GFS2: Prevent BUG from occurring when normal Withdraws occur Bob Peterson
2017-05-03 13:46 ` [Cluster-devel] [PATCH 2/9] gfs2: Replace rhashtable_walk_init with rhashtable_walk_enter Bob Peterson
2017-05-03 13:46 ` [Cluster-devel] [PATCH 3/9] gfs2: Deduplicate gfs2_{glocks, glstats}_open Bob Peterson
2017-05-03 13:46 ` Bob Peterson [this message]
2017-05-03 13:46 ` [Cluster-devel] [PATCH 5/9] GFS2: Temporarily zero i_no_addr when creating a dinode Bob Peterson
2017-05-03 13:46 ` [Cluster-devel] [PATCH 6/9] gfs2: Switch to rhashtable_lookup_get_insert_fast Bob Peterson
2017-05-03 13:46 ` [Cluster-devel] [PATCH 7/9] Revert "GFS2: Wait for iopen glock dequeues" Bob Peterson
2017-05-03 13:46 ` [Cluster-devel] [PATCH 8/9] gfs2: Re-enable fallocate for the rindex Bob Peterson
2017-05-03 13:46 ` [Cluster-devel] [PATCH 9/9] GFS2: Non-recursive delete Bob Peterson

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=20170503134608.31492-5-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).