cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Abhi Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 RFC PATCH 0/3] Locating jhead using a pool of bios
Date: Tue, 25 Sep 2018 00:38:50 -0500	[thread overview]
Message-ID: <1537853933-54390-1-git-send-email-adas@redhat.com> (raw)

This patchset does things a bit differently from the previous attempts
to find the journal head based on Andreas' suggestions.

It uses a pool of bios to maintain a readahead queue of sorts that allows
us to process the completed bios in sequential order to locate the jhead.

I've done a little bit of testing and it seems to be holding up so far.
I plan to do more testing.

I haven't done a performance analysis vs the old method yet, so I don't
know how well this does. There might be some optimizations we can do w.r.t
repeated allocations and such.

Abhi Das (3):
  gfs2: add more timing info to the journal recovery process
  gfs2: add a helper function to get_log_header that can be used
    elsewhere
  gfs2: introduce bio_pool to readahead journal to find jhead

 fs/gfs2/bmap.c       |   8 +-
 fs/gfs2/incore.h     |   3 +
 fs/gfs2/lops.c       | 359 +++++++++++++++++++++++++++++++++++++++++++++++++++
 fs/gfs2/lops.h       |   1 +
 fs/gfs2/ops_fstype.c |   2 +
 fs/gfs2/recovery.c   | 171 ++++++------------------
 fs/gfs2/recovery.h   |   2 +
 fs/gfs2/sys.c        |  27 ++--
 8 files changed, 433 insertions(+), 140 deletions(-)

-- 
2.4.11



             reply	other threads:[~2018-09-25  5:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  5:38 Abhi Das [this message]
2018-09-25  5:38 ` [Cluster-devel] [GFS2 RFC PATCH 1/3] gfs2: add more timing info to the journal recovery process Abhi Das
2018-09-25  5:38 ` [Cluster-devel] [GFS2 RFC PATCH 2/3] gfs2: add a helper function to get_log_header that can be used elsewhere Abhi Das
2018-09-25  5:38 ` [Cluster-devel] [GFS2 RFC PATCH 3/3] gfs2: introduce bio_pool to readahead journal to find jhead Abhi Das
2018-09-25  9:42   ` Steven Whitehouse

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=1537853933-54390-1-git-send-email-adas@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 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).