cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: reserve more blocks for transactions
Date: Tue, 21 Sep 2010 16:36:19 +0100	[thread overview]
Message-ID: <1285083379.2445.27.camel@dolmen> (raw)
In-Reply-To: <20100921145852.GA7185@ether.msp.redhat.com>

Hi,

On Tue, 2010-09-21 at 09:58 -0500, Benjamin Marzinski wrote:
> Some of the functions in GFS2 were not reserving space in the transaction for
> the resource group header and the resource groups bitblocks that get added
> when you do allocation. GFS2 now makes sure to reserve space for the
> resource group header and either all the bitblocks in the resource group, or
> one for each block that it may allocate, whichever is smaller.
> 
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
>  fs/gfs2/aops.c  |    3 +++
>  fs/gfs2/bmap.c  |    2 +-
>  fs/gfs2/file.c  |    5 ++++-
>  fs/gfs2/quota.c |    2 ++
>  4 files changed, 10 insertions(+), 2 deletions(-)
> 
> Index: gfs2-2.6-nmw/fs/gfs2/aops.c
> ===================================================================
> --- gfs2-2.6-nmw.orig/fs/gfs2/aops.c
> +++ gfs2-2.6-nmw/fs/gfs2/aops.c
> @@ -663,6 +663,9 @@ static int gfs2_write_begin(struct file 
>  		rblocks += RES_STATFS + RES_QUOTA;
>  	if (&ip->i_inode == sdp->sd_rindex)
>  		rblocks += 2 * RES_STATFS;
> +	if (alloc_required)
> +		rblocks += (al->al_requested < al->al_rgd->rd_length)?
> +			   al->al_requested + 1 : al->al_rgd->rd_length;
Since this bit seems to occur multiple times, perhaps you could turn it
into an inline function with a suitably explanatory name? That should
make it a bit easier to understand what it is doing,

Steve.

>  
>  	error = gfs2_trans_begin(sdp, rblocks,
>  				 PAGE_CACHE_SIZE/sdp->sd_sb.sb_bsize);
> Index: gfs2-2.6-nmw/fs/gfs2/bmap.c
> ===================================================================
> --- gfs2-2.6-nmw.orig/fs/gfs2/bmap.c
> +++ gfs2-2.6-nmw/fs/gfs2/bmap.c
> @@ -1151,7 +1151,7 @@ static int do_grow(struct inode *inode, 
>  			goto do_grow_qunlock;
>  	}
>  
> -	error = gfs2_trans_begin(sdp, RES_DINODE + 1, 0);
> +	error = gfs2_trans_begin(sdp, RES_DINODE + RES_STATFS + RES_RG_BIT, 0);
>  	if (error)
>  		goto do_grow_release;
>  
> Index: gfs2-2.6-nmw/fs/gfs2/file.c
> ===================================================================
> --- gfs2-2.6-nmw.orig/fs/gfs2/file.c
> +++ gfs2-2.6-nmw/fs/gfs2/file.c
> @@ -382,8 +382,11 @@ static int gfs2_page_mkwrite(struct vm_a
>  	rblocks = RES_DINODE + ind_blocks;
>  	if (gfs2_is_jdata(ip))
>  		rblocks += data_blocks ? data_blocks : 1;
> -	if (ind_blocks || data_blocks)
> +	if (ind_blocks || data_blocks) {
>  		rblocks += RES_STATFS + RES_QUOTA;
> +		rblocks += (al->al_requested < al->al_rgd->rd_length)?
> +			   al->al_requested + 1 : al->al_rgd->rd_length;
> +	}
>  	ret = gfs2_trans_begin(sdp, rblocks, 0);
>  	if (ret)
>  		goto out_trans_fail;
> Index: gfs2-2.6-nmw/fs/gfs2/quota.c
> ===================================================================
> --- gfs2-2.6-nmw.orig/fs/gfs2/quota.c
> +++ gfs2-2.6-nmw/fs/gfs2/quota.c
> @@ -1586,6 +1586,8 @@ static int gfs2_set_dqblk(struct super_b
>  		error = gfs2_inplace_reserve(ip);
>  		if (error)
>  			goto out_alloc;
> +		blocks += (al->al_requested < al->al_rgd->rd_length)?
> +			  al->al_requested + 1 : al->al_rgd->rd_length;
>  	}
>  
>  	error = gfs2_trans_begin(sdp, blocks + RES_DINODE + 1, 0);
> 




  reply	other threads:[~2010-09-21 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 14:58 [Cluster-devel] [PATCH] GFS2: reserve more blocks for transactions Benjamin Marzinski
2010-09-21 15:36 ` Steven Whitehouse [this message]
2010-09-21 15:40   ` Benjamin Marzinski

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=1285083379.2445.27.camel@dolmen \
    --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).