From: Abhijith Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 0/6] [resend] GFS2: Rework rgrp glock congestion functions for intra-node
Date: Thu, 11 Jan 2018 10:52:04 -0500 (EST) [thread overview]
Message-ID: <372990227.5487295.1515685924715.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180110204227.20315-1-rpeterso@redhat.com>
Hi,
Looks good to me. ACK.
Cheers!
--Abhi
----- Original Message -----
> From: "Bob Peterson" <rpeterso@redhat.com>
> To: "cluster-devel" <cluster-devel@redhat.com>
> Sent: Wednesday, January 10, 2018 2:42:21 PM
> Subject: [Cluster-devel] [GFS2 PATCH 0/6] [resend] GFS2: Rework rgrp glock congestion functions for intra-node
>
> On 06 November 2017, I posted this six-part patch set for rgrp glock
> congestion
> and got no response. I'm resending it here to give people one last
> opportunity to review it before I push it to the for-next branch. It has
> been rebased, but otherwise unchanged.
> ---
> Original patch set description:
>
> On 02 November, I posted a patch for this, but Steve Whitehouse pointed out
> a check that didn't look right. I tested it and found it to be unnecessary,
> so I remove it.
>
> Steve also pointed out that the patch tried to do too much. He asked which
> part of the patch actually made the performance gains.
>
> Based on Steve's suggestions, I've broken the changes into six patches for
> this
> patchset. The first five are all refactoring to make the code simpler and
> more easy to follow. Much of the complex special-case checks were
> consolidated
> from the variety of locations to more centralized functions. The actual
> performance gains are accomplished by the very last patch, "GFS2: Add checks
> for intra-node congestion". So strictly speaking, the last patch is the only
> patch we really need. But without the others, today's kludgy code becomes
> even more kludgy and harder to read.
>
> In doing all this, I did find a minor problem with the previous version's
> logic, and fixed it.
>
> I retested iozone performance and fragmentation. It is pretty much the same
> as I documented for the previous patch:
>
> Bob Peterson (6):
> GFS2: Simplify gfs2_rgrp_used_recently
> GFS2: Check gfs2_rgrp_used_recently inside gfs2_rgrp_congested
> GFS2: Refactor function fast_to_acquire
> GFS2: Simplify by checking fast_to_acquire in gfs2_rgrp_congested
> GFS2: Split gfs2_rgrp_congested into dlm and non-dlm cases
> GFS2: Add checks for intra-node congestion
>
> fs/gfs2/rgrp.c | 176
> +++++++++++++++++++++++++++++++++++++++++++--------------
> 1 file changed, 134 insertions(+), 42 deletions(-)
>
> --
> 2.14.3
>
>
prev parent reply other threads:[~2018-01-11 15:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 20:42 [Cluster-devel] [GFS2 PATCH 0/6] [resend] GFS2: Rework rgrp glock congestion functions for intra-node Bob Peterson
2018-01-10 20:42 ` [Cluster-devel] [GFS2 PATCH 1/6] GFS2: Simplify gfs2_rgrp_used_recently Bob Peterson
2018-01-10 20:42 ` [Cluster-devel] [GFS2 PATCH 2/6] GFS2: Check gfs2_rgrp_used_recently inside gfs2_rgrp_congested Bob Peterson
2018-01-12 10:45 ` Steven Whitehouse
2018-01-15 15:48 ` Bob Peterson
2018-01-10 20:42 ` [Cluster-devel] [GFS2 PATCH 3/6] GFS2: Refactor function fast_to_acquire Bob Peterson
2018-01-12 10:51 ` Steven Whitehouse
2018-01-15 16:00 ` Bob Peterson
2018-01-15 16:24 ` Bob Peterson
2018-01-10 20:42 ` [Cluster-devel] [GFS2 PATCH 4/6] GFS2: Simplify by checking fast_to_acquire in gfs2_rgrp_congested Bob Peterson
2018-01-12 10:55 ` Steven Whitehouse
2018-01-10 20:42 ` [Cluster-devel] [GFS2 PATCH 5/6] GFS2: Split gfs2_rgrp_congested into dlm and non-dlm cases Bob Peterson
2018-01-10 20:42 ` [Cluster-devel] [GFS2 PATCH 6/6] GFS2: Add checks for intra-node congestion Bob Peterson
2018-01-12 11:11 ` Steven Whitehouse
2018-01-11 15:52 ` Abhijith Das [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=372990227.5487295.1515685924715.JavaMail.zimbra@redhat.com \
--to=adas@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.