All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [gfs2-utils PATCH] fsck.gfs2: Issue read-ahead for dinodes in each bitmap
Date: Fri, 11 Jul 2014 17:07:51 +0100	[thread overview]
Message-ID: <53C00BD7.9030502@redhat.com> (raw)
In-Reply-To: <2099118726.6310652.1405011363612.JavaMail.zimbra@redhat.com>

Hi,

On 10/07/14 17:56, Bob Peterson wrote:
> Hi,
>
> This patch speeds up fsck.gfs2 by issuing read-ahead for each of the
> dinodes found in each of the bitmaps, prior to processing the bitmap.
Looks good to me,

Steve.

> Regards,
>
> Bob Peterson
> Red Hat File Systems
>
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> ---
>   gfs2/fsck/pass1.c | 4 ++++
>   1 file changed, 4 insertions(+)
>
> diff --git a/gfs2/fsck/pass1.c b/gfs2/fsck/pass1.c
> index fec2f64..90ca357 100644
> --- a/gfs2/fsck/pass1.c
> +++ b/gfs2/fsck/pass1.c
> @@ -1442,6 +1442,10 @@ static int pass1_process_bitmap(struct gfs2_sbd *sdp, struct rgrp_tree *rgd, uin
>   	struct gfs2_inode *ip;
>   	uint8_t q;
>   
> +	/* Issue read-ahead for all dinodes in this bitmap */
> +	for (i = 0; i < n; i++)
> +		posix_fadvise(sdp->device_fd, ibuf[i] * sdp->bsize, sdp->bsize,
> +			      POSIX_FADV_WILLNEED);
>   	for (i = 0; i < n; i++) {
>   		int is_inode;
>   		uint32_t check_magic;
>



      reply	other threads:[~2014-07-11 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1506544850.6310017.1405011313054.JavaMail.zimbra@redhat.com>
2014-07-10 16:56 ` [Cluster-devel] [gfs2-utils PATCH] fsck.gfs2: Issue read-ahead for dinodes in each bitmap Bob Peterson
2014-07-11 16:07   ` 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=53C00BD7.9030502@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 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.