From: Theodore Tso <tytso@mit.edu>
To: Valerie Aurora Henson <vaurora@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH, e2fsprogs] libext2fs: Add ext2fs_block_iterate3() which has 64-bit support
Date: Sat, 11 Oct 2008 07:32:36 -0400 [thread overview]
Message-ID: <20081011113236.GA12662@mit.edu> (raw)
In-Reply-To: <20081010220249.GA28360@shell>
On Fri, Oct 10, 2008 at 06:02:49PM -0400, Valerie Aurora Henson wrote:
> On Fri, Oct 10, 2008 at 04:43:43PM -0400, Theodore Ts'o wrote:
> >
> > There was discussion about how to do 64-bit ABI conversation, and an
> > assertion that it might be hard to do ext2fs_block_iterate3. So I
> > decided give an example of how I believe the most efficient way to do
> > this sort of thing.
>
> I'm afraid there's been a misunderstanding; I wasn't saying it was
> hard, just pointing out that different versions of interfaces are
> profilerating as a result of continuing to support the old ABI at the
> same time as the new 64-bit ABI - perhaps more versions of more
> functions than was originally anticipated. (I wrote a similar patch
> and I agree it's not hard, just more cruft to maintain.)
But it's not that much more cruft to maintain. Take a look at my
patch; the original interface gets implemented on top of the old
interface, so the amount of extra cruft to maintain is minimal. The
implementation of ext2fs_block_iterate2 simply becomes:
struct xlate64 xl;
xl.real_private = priv_data;
xl.func = func;
return ext2fs_block_iterate3(fs, ino, flags, block_buf,
xlate64_func, &xl);
That wasn't that bad, was it?
> Eagerly awaiting ext2fs_block_iterate4,
If there are other changes that we need to implement at the same time,
if we haven't done a release yet, we can fold those changes into the
ext2fs_block_iterate3.
- Ted
prev parent reply other threads:[~2008-10-11 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 20:43 [PATCH, e2fsprogs] libext2fs: Add ext2fs_block_iterate3() which has 64-bit support Theodore Ts'o
2008-10-10 22:02 ` Valerie Aurora Henson
2008-10-11 11:32 ` Theodore Tso [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=20081011113236.GA12662@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=vaurora@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.