From: Ted Ts'o <tytso@mit.edu>
To: Yongqiang Yang <xiaoqiangnk@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2] ext4:Teach ext4_ext_split to caculate extents efficiently.
Date: Tue, 24 May 2011 17:07:21 -0400 [thread overview]
Message-ID: <20110524210721.GD26055@thunk.org> (raw)
In-Reply-To: <1306143057-16962-1-git-send-email-xiaoqiangnk@gmail.com>
On Mon, May 23, 2011 at 05:30:57PM +0800, Yongqiang Yang wrote:
> @@ -982,20 +997,13 @@ static int ext4_ext_split(handle_t *handle, struct inode *inode,
> err = -EIO;
> goto cleanup;
> }
> - while (path[i].p_idx <= EXT_MAX_INDEX(path[i].p_hdr)) {
> - ext_debug("%d: move %d:%llu in new index %llu\n", i,
> - le32_to_cpu(path[i].p_idx->ei_block),
> - ext4_idx_pblock(path[i].p_idx),
> - newblock);
> - /*memmove(++fidx, path[i].p_idx++,
> - sizeof(struct ext4_extent_idx));
> - neh->eh_entries++;
> - BUG_ON(neh->eh_entries > neh->eh_max);*/
> - path[i].p_idx++;
> - m++;
> - }
> + /* start copy indexes */
> + m = EXT_MAX_INDEX(path[i].p_hdr) - path[i].p_idx++;
> + ext_debug("cur 0x%p, last 0x%p\n", path[i].p_idx,
> + EXT_MAX_INDEX(path[i].p_hdr));
> + ext4_ext_show_move(inode, path, newblock, i);
> if (m) {
> - memmove(++fidx, path[i].p_idx - m,
> + memmove(++fidx, path[i].p_idx,
> sizeof(struct ext4_extent_idx) * m);
> le16_add_cpu(&neh->eh_entries, m);
> }
So the old code mutates path[i].p_idx, where as your new code doesn't.
The one thing that scares me is that ext4_ext_insert_index() is passed
&path[at], the function preferences path[at].p_idx.
Have you looked at this case?
- Ted
next prev parent reply other threads:[~2011-05-24 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 9:30 [PATCH v2] ext4:Teach ext4_ext_split to caculate extents efficiently Yongqiang Yang
2011-05-24 21:07 ` Ted Ts'o [this message]
2011-05-25 2:02 ` Yongqiang Yang
2011-05-25 22:02 ` Ted Ts'o
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=20110524210721.GD26055@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=xiaoqiangnk@gmail.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.