From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao2.yu@samsung.com>
Cc: Changman Lee <cm224.lee@samsung.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev][PATCH] f2fs: merge two uchar variable in struct nat_entry to reduce memory cost
Date: Mon, 15 Dec 2014 00:27:17 -0800 [thread overview]
Message-ID: <20141215082717.GA83773@jaegeuk-mac02.mot-mobility.com> (raw)
In-Reply-To: <001c01d012b6$a0fbaaa0$e2f2ffe0$@samsung.com>
Hi Chao,
I found a bug in this patch.
In set_node_addr,
down_write(&nm_i->nat_tree_lock);
e = __lookup_nat_cache(nm_i, ni->nid);
if (!e) {
e = grab_nat_entry(nm_i, ni->nid);
e->ni = *ni;
^^^^^^^^^^^^
this line should not copy ni.flag.
f2fs_bug_on(sbi, ni->blk_addr == NEW_ADDR);
} else if (new_blkaddr == NEW_ADDR) {
/*
* when nid is reallocated,
* previous nat entry can be remained in nat cache.
* So, reinitialize it with new information.
*/
e->ni = *ni;
^^^^^^^^^^^^
ditto.
f2fs_bug_on(sbi, ni->blk_addr != NULL_ADDR);
}
So, please add inline function in node.h like:
static inline void copy_node_info(dst, src)
{
dst->nid = src->nid;
dst->ino = src->ino;
dst->blk_addr = src->blk_addr;
dst->version = src->version;
/* should not copy flag here */
}
Then let's use this function.
Thanks,
On Mon, Dec 08, 2014 at 03:13:49PM +0800, Chao Yu wrote:
> This patch moves one member of struct nat_entry: _flag_ to struct node_info,
> so _version_ in struct node_info and _flag_ with unsigned char type will merge
> to one 32-bit space in register/memory. Then the size of nat_entry will reduce
> its size from 28 bytes to 24 bytes and slab memory using by f2fs will be
> reduced.
>
> Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> ---
> fs/f2fs/node.h | 23 ++++++++++++-----------
> 1 file changed, 12 insertions(+), 11 deletions(-)
>
> diff --git a/fs/f2fs/node.h b/fs/f2fs/node.h
> index d10b644..27a7318 100644
> --- a/fs/f2fs/node.h
> +++ b/fs/f2fs/node.h
> @@ -29,6 +29,14 @@
> /* return value for read_node_page */
> #define LOCKED_PAGE 1
>
> +/* For flag in struct node_info */
> +enum {
> + IS_CHECKPOINTED, /* is it checkpointed before? */
> + HAS_FSYNCED_INODE, /* is the inode fsynced before? */
> + HAS_LAST_FSYNC, /* has the latest node fsync mark? */
> + IS_DIRTY, /* this nat entry is dirty? */
> +};
> +
> /*
> * For node information
> */
> @@ -37,18 +45,11 @@ struct node_info {
> nid_t ino; /* inode number of the node's owner */
> block_t blk_addr; /* block address of the node */
> unsigned char version; /* version of the node */
> -};
> -
> -enum {
> - IS_CHECKPOINTED, /* is it checkpointed before? */
> - HAS_FSYNCED_INODE, /* is the inode fsynced before? */
> - HAS_LAST_FSYNC, /* has the latest node fsync mark? */
> - IS_DIRTY, /* this nat entry is dirty? */
> + unsigned char flag; /* for node information bits */
> };
>
> struct nat_entry {
> struct list_head list; /* for clean or dirty nat list */
> - unsigned char flag; /* for node information bits */
> struct node_info ni; /* in-memory node information */
> };
>
> @@ -68,15 +69,15 @@ static inline void set_nat_flag(struct nat_entry *ne,
> {
> unsigned char mask = 0x01 << type;
> if (set)
> - ne->flag |= mask;
> + ne->ni.flag |= mask;
> else
> - ne->flag &= ~mask;
> + ne->ni.flag &= ~mask;
> }
>
> static inline bool get_nat_flag(struct nat_entry *ne, unsigned int type)
> {
> unsigned char mask = 0x01 << type;
> - return ne->flag & mask;
> + return ne->ni.flag & mask;
> }
>
> static inline void nat_reset_flag(struct nat_entry *ne)
> --
> 2.1.2
next prev parent reply other threads:[~2014-12-15 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 7:13 Chao Yu
2014-12-15 8:27 ` Jaegeuk Kim [this message]
2014-12-15 9:16 ` Chao Yu
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=20141215082717.GA83773@jaegeuk-mac02.mot-mobility.com \
--to=jaegeuk@kernel.org \
--cc=chao2.yu@samsung.com \
--cc=cm224.lee@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®