From: David Sterba <dsterba@suse.cz>
To: Filipe David Borba Manana <fdmanana@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] Btrfs: remove unneeded field / smaller extent_map structure
Date: Wed, 26 Feb 2014 19:23:21 +0100 [thread overview]
Message-ID: <20140226182321.GH16073@twin.jikos.cz> (raw)
In-Reply-To: <1393337713-5991-1-git-send-email-fdmanana@gmail.com>
On Tue, Feb 25, 2014 at 02:15:12PM +0000, Filipe David Borba Manana wrote:
> We don't need to have an unsigned int field in the extent_map struct
> to tell us whether the extent map is in the inode's extent_map tree or
> not. We can use the rb_node struct field and the RB_CLEAR_NODE and
> RB_EMPTY_NODE macros to achieve the same task.
>
> This reduces sizeof(struct extent_map) from 152 bytes to 144 bytes (on a
> 64 bits system).
>
> Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
Reviewed-by: David Sterba <dsterba@suse.cz>
prev parent reply other threads:[~2014-02-26 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 14:15 [PATCH 1/2] Btrfs: remove unneeded field / smaller extent_map structure Filipe David Borba Manana
2014-02-25 14:15 ` [PATCH 2/2] Btrfs: more efficient btrfs_drop_extent_cache Filipe David Borba Manana
2014-02-26 18:23 ` David Sterba [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=20140226182321.GH16073@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@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