From: "Jose R. Santos" <jrs@us.ibm.com>
To: Josef Bacik <jbacik@redhat.com>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [RFC][PATCH 2/2] convert alloc.c to use blk64_t
Date: Fri, 11 Apr 2008 11:55:12 -0500 [thread overview]
Message-ID: <20080411115512.02167595@gara.konoha.net> (raw)
In-Reply-To: <20080411153616.GB32661@unused.rdu.redhat.com>
On Fri, 11 Apr 2008 11:36:16 -0400
Josef Bacik <jbacik@redhat.com> wrote:
> Hello,
>
>
> commit 0b80dee54f94f13210ae87a504e3b49d3dc284d4
> Author: Josef Bacik <jbacik@redhat.com>
> Date: Fri Apr 11 18:23:13 2008 -0400
>
> Convert the block alloc functions to be 64bit capable.
>
> Signed-off-by: Josef Bacik <jbacik@redhat.com>
>
> diff --git a/lib/ext2fs/alloc.c b/lib/ext2fs/alloc.c
> index 65f3ea1..6924457 100644
> --- a/lib/ext2fs/alloc.c
> +++ b/lib/ext2fs/alloc.c
> @@ -73,10 +73,10 @@ errcode_t ext2fs_new_inode(ext2_filsys fs, ext2_ino_t dir,
> * Stupid algorithm --- we now just search forward starting from the
> * goal. Should put in a smarter one someday....
> */
> -errcode_t ext2fs_new_block(ext2_filsys fs, blk_t goal,
> - ext2fs_block_bitmap map, blk_t *ret)
> +errcode_t ext2fs_new_block64(ext2_filsys fs, blk64_t goal,
> + ext2fs_block_bitmap map, blk64_t *ret)
This should be ext2fs_new_blocks2() to make it easier to expand the API
in the future. Using ext2fs_new_block64_2() just looks weird if we
ever needed to change the ABI requiring a new call.
> diff --git a/lib/ext2fs/ext2fs.h b/lib/ext2fs/ext2fs.h
> index a60e28b..058dea7 100644
> --- a/lib/ext2fs/ext2fs.h
> +++ b/lib/ext2fs/ext2fs.h
> @@ -1385,6 +1385,17 @@ _INLINE_ blk64_t ext2fs_inode_data_blocks64(ext2_filsys fs,
> return ret;
> }
>
> +/*
> + * Return the s_blocks_count in 64 bit
> + */
> +_INLINE_ blk64_t ext2fs_super_blocks_count(ext2_filsys fs)
> +{
> + if (fs->super->s_feature_incompat & EXT4_FEATURE_INCOMPAT_64BIT)
> + return (((blk64_t)fs->super->s_blocks_count << 32) |
> + fs->super->s_blocks_count);
> + return fs->super->s_blocks_count;
> +}
> +
> #undef _INLINE_
> #endif
Shouldn't this pe bart of your previous patch?
-JRS
prev parent reply other threads:[~2008-04-11 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 15:36 [RFC][PATCH 2/2] convert alloc.c to use blk64_t Josef Bacik
2008-04-11 16:55 ` Jose R. Santos [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=20080411115512.02167595@gara.konoha.net \
--to=jrs@us.ibm.com \
--cc=jbacik@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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