cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v2 0/6] gfs2: Prepare for resource group glock sharing
Date: Sat,  1 Dec 2018 12:10:13 +0100	[thread overview]
Message-ID: <20181201111019.14363-1-agruenba@redhat.com> (raw)

This is an update of the resource group glock sharing patch queue by Bob
and myself.  Some of the cleanups and fixes posted previously [*] have
been integrated upstream in the meantime.

Patch "gfs2: Add local resource group locking" is now built on top of
the existing rgrp locking scheme; I'll get back to cleaning that up
later.

Steve was questioning the performance impact of patch "gfs2: Only use
struct gfs2_rbm for bitmap manipulations".  I still think it's a
non-issue, but some analysis will be useful.

This updated patch queue has passed initial testing.

Thanks,
Andreas

[*] https://www.redhat.com/archives/cluster-devel/2018-October/msg00006.html

Andreas Gruenbacher (3):
  gfs2: Only use struct gfs2_rbm for bitmap manipulations
  gfs2: Clean up gfs2_adjust_reservation
  gfs2: Add per-reservation reserved block accounting

Bob Peterson (3):
  gfs2: Add local resource group locking
  gfs2: Allow node-wide exclusive glock sharing
  gfs2: Introduce resource group sharing

 fs/gfs2/bmap.c       |   4 +-
 fs/gfs2/file.c       |   4 +-
 fs/gfs2/glock.c      |  26 +++-
 fs/gfs2/glock.h      |   6 +
 fs/gfs2/incore.h     |  33 +----
 fs/gfs2/inode.c      |   5 +-
 fs/gfs2/lops.c       |   5 +-
 fs/gfs2/rgrp.c       | 322 ++++++++++++++++++++++++++++---------------
 fs/gfs2/rgrp.h       |   4 +
 fs/gfs2/super.c      |   3 +-
 fs/gfs2/trace_gfs2.h |  18 ++-
 fs/gfs2/trans.h      |   2 +-
 fs/gfs2/xattr.c      |   6 +-
 13 files changed, 279 insertions(+), 159 deletions(-)

-- 
2.19.1.546.g028f9c799.dirty



             reply	other threads:[~2018-12-01 11:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-01 11:10 Andreas Gruenbacher [this message]
2018-12-01 11:10 ` [Cluster-devel] [PATCH v2 1/6] gfs2: Only use struct gfs2_rbm for bitmap manipulations Andreas Gruenbacher
2018-12-01 11:10 ` [Cluster-devel] [PATCH v2 2/6] gfs2: Clean up gfs2_adjust_reservation Andreas Gruenbacher
2018-12-03 14:32   ` Bob Peterson
2018-12-03 14:58     ` Andreas Gruenbacher
2018-12-04 22:02   ` Andreas Gruenbacher
2018-12-01 11:10 ` [Cluster-devel] [PATCH v2 3/6] gfs2: Add per-reservation reserved block accounting Andreas Gruenbacher
2018-12-01 11:10 ` [Cluster-devel] [PATCH v2 4/6] gfs2: Add local resource group locking Andreas Gruenbacher
2018-12-01 11:10 ` [Cluster-devel] [PATCH v2 5/6] gfs2: Allow node-wide exclusive glock sharing Andreas Gruenbacher
2018-12-01 11:10 ` [Cluster-devel] [PATCH v2 6/6] gfs2: Introduce resource group sharing 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=20181201111019.14363-1-agruenba@redhat.com \
    --to=agruenba@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).