From: Chris Mason <chris.mason@oracle.com>
To: Liu Bo <liubo2009@cn.fujitsu.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
t-itoh <t-itoh@jp.fujitsu.com>, dave <dave@jikos.cz>
Subject: Re: [PATCH 1/2 v2] Btrfs: kill location key of in-memory inode
Date: Mon, 27 Jun 2011 21:54:16 -0400 [thread overview]
Message-ID: <1309226015-sup-8915@shiny> (raw)
In-Reply-To: <1308538756-31203-1-git-send-email-liubo2009@cn.fujitsu.com>
Excerpts from Liu Bo's message of 2011-06-19 22:59:15 -0400:
> In btrfs's in-memory inode, there is a btrfs_key which has the structure:
> - key.objectid
> - key.type
> - key.offset
>
> however, we only use key.objectid to search, to check or something else,
> and to reduce in-memory inode size I just keep what is valuable.
I'm still reviewing this, mostly because I had plans on using the full
location as part of the inodes for tree roots. But this might not
really be required anymore.
-chris
prev parent reply other threads:[~2011-06-28 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 2:59 [PATCH 1/2 v2] Btrfs: kill location key of in-memory inode Liu Bo
2011-06-20 2:59 ` [PATCH 2/2 v2] Btrfs: fix 'ls -lis' mismatch Liu Bo
2011-06-28 1:44 ` [PATCH 1/2 v2] Btrfs: kill location key of in-memory inode liubo
2011-06-28 1:54 ` Chris Mason [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=1309226015-sup-8915@shiny \
--to=chris.mason@oracle.com \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.com \
--cc=t-itoh@jp.fujitsu.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 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).