From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 0/4] Speed up journal head lookup
Date: Fri, 7 Sep 2018 09:53:26 +0100 [thread overview]
Message-ID: <58268f2e-b940-d2fb-ab6c-a63bd4031e76@redhat.com> (raw)
In-Reply-To: <1536253357-8967-1-git-send-email-adas@redhat.com>
Hi,
On 06/09/18 18:02, Abhi Das wrote:
> This is the upstream version of the rhel7 patchset I'd
> posted earlier for review.
>
> It is slightly different in parts owing to some bits
> already being present and the hash/crc computation code
> being different due to the updated log header structure.
>
> Cheers!
> --Abhi
Looks good. Thanks for sorting this out, it should be a good base on
which to build future improvements. Lets make sure it gets lots of testing,
Steve.
>
> *** BLURB HERE ***
>
> Abhi Das (4):
> gfs2: add timing info to map_journal_extents
> gfs2: changes to gfs2_log_XXX_bio
> gfs2: add a helper function to get_log_header that can be used
> elsewhere
> gfs2: read journal in large chunks to locate the head
>
> fs/gfs2/bmap.c | 8 ++-
> fs/gfs2/incore.h | 8 ++-
> fs/gfs2/log.c | 4 +-
> fs/gfs2/lops.c | 142 ++++++++++++++++++++++++++++++++++++-------
> fs/gfs2/lops.h | 3 +-
> fs/gfs2/ops_fstype.c | 1 +
> fs/gfs2/recovery.c | 168 +++++++++++++--------------------------------------
> fs/gfs2/recovery.h | 2 +
> 8 files changed, 184 insertions(+), 152 deletions(-)
>
prev parent reply other threads:[~2018-09-07 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 17:02 [Cluster-devel] [GFS2 PATCH 0/4] Speed up journal head lookup Abhi Das
2018-09-06 17:02 ` [Cluster-devel] [GFS2 PATCH 1/4] gfs2: add timing info to map_journal_extents Abhi Das
2018-09-06 17:02 ` [Cluster-devel] [GFS2 PATCH 2/4] gfs2: changes to gfs2_log_XXX_bio Abhi Das
2018-09-06 17:02 ` [Cluster-devel] [GFS2 PATCH 3/4] gfs2: add a helper function to get_log_header that can be used elsewhere Abhi Das
2018-09-06 17:02 ` [Cluster-devel] [GFS2 PATCH 4/4] gfs2: read journal in large chunks to locate the head Abhi Das
2018-09-07 12:14 ` Andreas Gruenbacher
2018-09-07 12:51 ` Abhijith Das
2018-09-07 12:46 ` Bob Peterson
2018-09-07 8:53 ` Steven Whitehouse [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=58268f2e-b940-d2fb-ab6c-a63bd4031e76@redhat.com \
--to=swhiteho@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).