From: Valerie Clement <valerie.clement@bull.net>
To: Avantika Mathur <mathur@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH, RFC 1/3] ext4_grpnum_t: Add new type
Date: Wed, 10 Oct 2007 11:42:43 +0200 [thread overview]
Message-ID: <470C9E93.8050709@bull.net> (raw)
In-Reply-To: <4702E340.8070603@linux.vnet.ibm.com>
Avantika Mathur wrote:
> Ext4: add new type ext4_grpnum_t, and change all group variables to this
> type.
> from: mathur@us.ibm.com
> In many places variables for block group are of type int, which limits the
> maximum filesystem size. This patch introduces a new type
> ext4_grpnum_t, of type unsigned long, to represent block group numbers
> in ext4.
> All occurrences of block group variables are converted to type
> ext4_grpnum_t.
Hi avantika,
Just one little thing, you forgot to convert a variable type in balloc.c:
ext4_fsblk_t ext4_new_blocks_old(handle_t *handle, struct inode *inode,
ext4_fsblk_t goal, unsigned long *count, int *errp)
{
struct buffer_head *bitmap_bh = NULL;
struct buffer_head *gdp_bh;
ext4_grpnum_t group_no;
ext4_grpnum_t goal_group;
ext4_grpblk_t grp_target_blk; /* blockgroup relative goal
block */
ext4_grpblk_t grp_alloc_blk; /* blockgroup-relative
allocated block*/
ext4_fsblk_t ret_block; /* filesyetem-wide allocated
block */
int bgi; /* blockgroup iteration index */
^^^^^
Could you also remove, at the same time, the useless lines in this function:
#ifdef EXT4FS_DEBUG
static int goal_hits, goal_attempts;
#endif
... and:
ext4_debug("allocating block %lu. Goal hits %d of %d.\n",
ret_block, goal_hits, goal_attempts);
Just to clean up the code.
Thanks,
Valérie
next prev parent reply other threads:[~2007-10-10 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 0:33 [PATCH, RFC 1/3] ext4_grpnum_t: Add new type Avantika Mathur
2007-10-10 9:42 ` Valerie Clement [this message]
2007-10-12 21:46 ` Avantika Mathur
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=470C9E93.8050709@bull.net \
--to=valerie.clement@bull.net \
--cc=linux-ext4@vger.kernel.org \
--cc=mathur@linux.vnet.ibm.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).