From: Eric Sandeen <sandeen@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: sho@tnes.nec.co.jp, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH 2/3] Move the file data to the new blocks
Date: Tue, 06 Feb 2007 21:45:37 -0600 [thread overview]
Message-ID: <45C94B61.4070105@redhat.com> (raw)
In-Reply-To: <20070206173344.a3e8e37a.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Tue, 16 Jan 2007 21:05:20 +0900
> sho@tnes.nec.co.jp wrote:
...
>> +ext4_ext_replace_branches(struct inode *org_inode, struct inode *dest_inode,
>> + pgoff_t from_page, pgoff_t dest_from_page,
>> + pgoff_t count_page, unsigned long *delete_start)
>> +{
>> + struct ext4_ext_path *org_path = NULL;
>> + struct ext4_ext_path *dest_path = NULL;
>> + struct ext4_extent *oext, *dext;
>> + struct ext4_extent tmp_ext;
>> + int err = 0;
>> + int depth;
>> + unsigned long from, count, dest_off, diff, replaced_count = 0;
>
> These should be sector_t, shouldn't they?
At some point should we start using blkcnt_t properly?
(block-in[-large]-file, not block-in[-large]-device?) I think that's
what it was introduced for, although it's not in wide use at this point.
I guess the type really isn't used anywhere else; just in the inode's
i_blocks. Hmm.
-Eric
next prev parent reply other threads:[~2007-02-07 3:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 12:05 [RFC][PATCH 2/3] Move the file data to the new blocks sho
2007-02-05 13:12 ` Jan Kara
2007-02-05 22:06 ` Nathan Scott
2007-02-07 1:35 ` Andrew Morton
2007-02-07 20:46 ` Andreas Dilger
2007-02-07 20:56 ` Andrew Morton
2007-02-08 9:29 ` Jan Kara
2007-02-08 9:45 ` Andrew Morton
2007-02-08 10:21 ` Jan Kara
2007-02-08 10:32 ` Andrew Morton
2007-02-08 10:47 ` Jan Kara
2007-02-12 3:11 ` Theodore Tso
2007-02-07 1:33 ` Andrew Morton
2007-02-07 3:45 ` Eric Sandeen [this message]
2007-02-07 9:46 ` Takashi Sato
-- strict thread matches above, loose matches on Subject: below --
2007-02-08 9:01 Takashi Sato
2006-12-22 10:30 sho
2006-11-09 11:10 sho
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=45C94B61.4070105@redhat.com \
--to=sandeen@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sho@tnes.nec.co.jp \
/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).