From: Theodore Ts'o <tytso@mit.edu>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org, lczerner@redhat.com
Subject: Re: [PATCH 1/2] Use ext4_ext_next_allocated_block instead of mext_next_extent -v2
Date: Sun, 31 Aug 2014 15:23:40 -0400 [thread overview]
Message-ID: <20140831192340.GG8974@thunk.org> (raw)
In-Reply-To: <1408195026-2313-1-git-send-email-dmonakhov@openvz.org>
On Sat, Aug 16, 2014 at 05:17:05PM +0400, Dmitry Monakhov wrote:
> This allow to make mext_next_extent static and potentially get rid of it.
>
> Changes from v1-v2:
> - Optimize traversing inside one leaf (in response to lczerner@ comments)
>
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
Applied, thanks.
- Ted
prev parent reply other threads:[~2014-08-31 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 13:17 [PATCH 1/2] Use ext4_ext_next_allocated_block instead of mext_next_extent -v2 Dmitry Monakhov
2014-08-16 13:17 ` [PATCH 2/2] ext4: refactor ext4_move_extents code base v5 Dmitry Monakhov
2014-08-31 19:48 ` Theodore Ts'o
2014-08-31 19:23 ` Theodore Ts'o [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=20140831192340.GG8974@thunk.org \
--to=tytso@mit.edu \
--cc=dmonakhov@openvz.org \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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).