From: Valerie Aurora Henson <vaurora@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, "Jose R. Santos" <jrs@us.ibm.com>
Subject: Re: 64-bit dblists
Date: Wed, 12 Nov 2008 11:48:36 -0500 [thread overview]
Message-ID: <20081112164836.GF29956@shell> (raw)
In-Reply-To: <20081103030936.GB29102@mit.edu>
On Sun, Nov 02, 2008 at 10:09:36PM -0500, Theodore Tso wrote:
> On Mon, Oct 27, 2008 at 04:59:10PM -0400, Valerie Aurora Henson wrote:
> > Hi all,
> >
> > In my continuing quest to finish the 64-bit conversion of e2fsprogs, I
> > ran into this structure exported in ext2fs.h:
> >
> > struct ext2_db_entry {
> > ext2_ino_t ino;
> > blk_t blk;
> > int blockcnt;
> > };
> >
> > The "blk_t" is the problem here - we need a blk64_t. A pointer to
> > this structure is passed to the user-provided directory block iterator
> > in ext2fs_dblist_iterate().
> >
> > Assuming the goal is to preserve the ext2fs_dblist ABI, I can see two
> > ways of doing this:
> >
> > 1. Define ext2_db_entry2, ext2_dblist2, and ext2fs_dblist_*2() and do
> > the usual translation/conversion function business.
>
> The dblist.c and dblist_dir.c functions are so small that it's
> probably not worth it to do translaction/conversation functions; it's
> basically just a linked list convenience function implementation.
>
> My suggestion is to just create a dblist2.c and dblist_dir2.c, and
> just make a 64-bit version of the directory block list abstraction.
> My guess that size of the conversaion functions would be bigger than a
> new 64-bit version of the abstraction. (The object size of dblist.o
> and dblist_dir.o combined is only about 1.5k)
Thanks! This is what I'm doing currently.
-VAL
prev parent reply other threads:[~2008-11-12 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 20:59 64-bit dblists Valerie Aurora Henson
2008-11-03 3:09 ` Theodore Tso
2008-11-12 16:48 ` Valerie Aurora Henson [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=20081112164836.GF29956@shell \
--to=vaurora@redhat.com \
--cc=jrs@us.ibm.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 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.