From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Don't pack struct lm_lockname
Date: Thu, 16 Mar 2017 12:18:03 +0000 [thread overview]
Message-ID: <bd85bbc2-0fcf-e4d7-fa63-143f494aa2c9@redhat.com> (raw)
In-Reply-To: <1489603738-27603-1-git-send-email-agruenba@redhat.com>
On 15/03/17 18:48, Andreas Gruenbacher wrote:
> As per a suggestion by Linus, don't pack struct lm_lockname: we did that
> because the struct 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>
Tested-by: Andrew Price <anprice@redhat.com>
Andy
> ---
> 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 ec0848f..903c853 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) && \
>
next prev parent reply other threads:[~2017-03-16 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 18:48 [Cluster-devel] [PATCH] gfs2: Don't pack struct lm_lockname Andreas Gruenbacher
2017-03-16 12:18 ` Andrew Price [this message]
2017-03-16 14:11 ` 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=bd85bbc2-0fcf-e4d7-fa63-143f494aa2c9@redhat.com \
--to=anprice@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.