From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RFC PATCH 1/3] gfs2: allow map_journal_extents() to take a journal descriptor as argument
Date: Tue, 29 May 2018 10:57:51 +0100 [thread overview]
Message-ID: <dffbaeb1-d8b0-fbae-71ed-2603553f5b83@redhat.com> (raw)
In-Reply-To: <1527581147-25544-2-git-send-email-adas@redhat.com>
Hi,
Looks good.
Acked-by: Steven Whitehouse <swhiteho@redhat.com>
Steve.
On 29/05/18 09:05, Abhi Das wrote:
> This function now maps the extents for the journal whose descriptor
> is passed in as argument.
>
> Signed-off-by: Abhi Das <adas@redhat.com>
> ---
> fs/gfs2/log.h | 1 +
> fs/gfs2/ops_fstype.c | 5 ++---
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/gfs2/log.h b/fs/gfs2/log.h
> index 92dcbe7..19c93df 100644
> --- a/fs/gfs2/log.h
> +++ b/fs/gfs2/log.h
> @@ -75,4 +75,5 @@ extern int gfs2_logd(void *data);
> extern void gfs2_add_revoke(struct gfs2_sbd *sdp, struct gfs2_bufdata *bd);
> extern void gfs2_write_revokes(struct gfs2_sbd *sdp);
>
> +extern int map_journal_extents(struct gfs2_sbd *sdp, struct gfs2_jdesc *jd);
> #endif /* __LOG_DOT_H__ */
> diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
> index 228f38e..cf3e366 100644
> --- a/fs/gfs2/ops_fstype.c
> +++ b/fs/gfs2/ops_fstype.c
> @@ -524,9 +524,8 @@ out:
> * but since it's only done at mount time, I'm not worried about the
> * time it takes.
> */
> -static int map_journal_extents(struct gfs2_sbd *sdp)
> +int map_journal_extents(struct gfs2_sbd *sdp, struct gfs2_jdesc *jd)
> {
> - struct gfs2_jdesc *jd = sdp->sd_jdesc;
> unsigned int lb;
> u64 db, prev_db; /* logical block, disk block, prev disk block */
> struct gfs2_inode *ip = GFS2_I(jd->jd_inode);
> @@ -772,7 +771,7 @@ static int init_journal(struct gfs2_sbd *sdp, int undo)
> atomic_set(&sdp->sd_log_thresh2, 4*sdp->sd_jdesc->jd_blocks/5);
>
> /* Map the extents for this journal's blocks */
> - map_journal_extents(sdp);
> + map_journal_extents(sdp, sdp->sd_jdesc);
> }
> trace_gfs2_log_blocks(sdp, atomic_read(&sdp->sd_log_blks_free));
>
next prev parent reply other threads:[~2018-05-29 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 8:05 [Cluster-devel] [RFC PATCH 0/3] Speed up journal head lookup Abhi Das
2018-05-29 8:05 ` [Cluster-devel] [RFC PATCH 1/3] gfs2: allow map_journal_extents() to take a journal descriptor as argument Abhi Das
2018-05-29 9:57 ` Steven Whitehouse [this message]
2018-05-29 8:05 ` [Cluster-devel] [RFC PATCH 2/3] gfs2: add timing info for various stages of journal recovery Abhi Das
2018-05-29 9:59 ` Steven Whitehouse
2018-05-29 8:05 ` [Cluster-devel] [RFC PATCH 3/3] gfs2: read journal in large chunks to locate the head Abhi Das
2018-05-29 10:15 ` Steven Whitehouse
2018-05-29 9:57 ` [Cluster-devel] [RFC PATCH 0/3] Speed up journal head lookup 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=dffbaeb1-d8b0-fbae-71ed-2603553f5b83@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).