From: tytso@mit.edu
To: Akira Fujita <a-fujita@rs.jp.nec.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 3/3]ext4: move_extent_per_page() cleanup
Date: Tue, 24 Nov 2009 10:32:33 -0500 [thread overview]
Message-ID: <20091124153233.GL2183@thunk.org> (raw)
In-Reply-To: <4B03A197.5030605@rs.jp.nec.com>
On Wed, Nov 18, 2009 at 04:26:15PM +0900, Akira Fujita wrote:
> ext4: move_extent_per_page() cleanup
>
> From: Akira Fujita <a-fujita@rs.jp.nec.com>
>
> This is a cleanup patch.
> Integrate duplicate lines (acquire/release semaphore
> and invalidate extent cache in move_extent_per_page())
> into mext_replace_branches(),
> so this change leads to the code size reduction.
Applied to the ext4 patch queue with the following rewording of the
commit description:
ext4: move_extent_per_page() cleanup
From: Akira Fujita <a-fujita@rs.jp.nec.com>
Integrate duplicate lines (acquire/release semaphore and invalidate
extent cache in move_extent_per_page()) into mext_replace_branches(),
to reduce source and object code size.
Signed-off-by: Akira Fujita <a-fujita@rs.jp.nec.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
- Ted
prev parent reply other threads:[~2009-11-24 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 7:26 [PATCH 3/3]ext4: move_extent_per_page() cleanup Akira Fujita
2009-11-24 15:32 ` tytso [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=20091124153233.GL2183@thunk.org \
--to=tytso@mit.edu \
--cc=a-fujita@rs.jp.nec.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 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.