From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Yunlong Song <yunlong.song@huawei.com>
Cc: cm224.lee@samsung.com, yuchao0@huawei.com, chao@kernel.org,
sylinux@163.com, miaoxie@huawei.com, bintian.wang@huawei.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] f2fs: change the codes of checking CP_CRC_RECOVERY_FLAG to macro
Date: Sat, 25 Feb 2017 10:46:19 -0800 [thread overview]
Message-ID: <20170225184619.GC51627@jaegeuk.local> (raw)
In-Reply-To: <1488009678-17334-1-git-send-email-yunlong.song@huawei.com>
On 02/25, Yunlong Song wrote:
> No need to check the "if" condition each time, just change it to macro codes.
>
> Signed-off-by: Yunlong Song <yunlong.song@huawei.com>
> ---
> fs/f2fs/node.h | 10 +++++-----
> fs/f2fs/segment.c | 5 +++--
> 2 files changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/fs/f2fs/node.h b/fs/f2fs/node.h
> index 3fc9c4b..caebb23 100644
> --- a/fs/f2fs/node.h
> +++ b/fs/f2fs/node.h
> @@ -303,11 +303,11 @@ static inline void fill_node_footer_blkaddr(struct page *page, block_t blkaddr)
> size_t crc_offset = le32_to_cpu(ckpt->checksum_offset);
> __u64 cp_ver = le64_to_cpu(ckpt->checkpoint_ver);
>
> - if (__is_set_ckpt_flags(ckpt, CP_CRC_RECOVERY_FLAG)) {
> - __u64 crc = le32_to_cpu(*((__le32 *)
> - ((unsigned char *)ckpt + crc_offset)));
> - cp_ver |= (crc << 32);
> - }
> +#ifdef CP_CRC_RECOVERY_FLAG
NAK.
This is not a kernel config, nor a recommendable coding style.
Moreover, it is simply able to be defined through header file in old kernel.
Thanks,
> + __u64 crc = le32_to_cpu(*((__le32 *)
> + ((unsigned char *)ckpt + crc_offset)));
> + cp_ver |= (crc << 32);
> +#endif
> rn->footer.cp_ver = cpu_to_le64(cp_ver);
> rn->footer.next_blkaddr = cpu_to_le32(blkaddr);
> }
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 9eb6d89..6c2e1ee 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -1573,9 +1573,10 @@ static void allocate_segment_by_default(struct f2fs_sb_info *sbi,
> {
> if (force)
> new_curseg(sbi, type, true);
> - else if (!is_set_ckpt_flags(sbi, CP_CRC_RECOVERY_FLAG) &&
> - type == CURSEG_WARM_NODE)
> +#ifndef CP_CRC_RECOVERY_FLAG
> + else if (type == CURSEG_WARM_NODE)
> new_curseg(sbi, type, false);
> +#endif
> else if (need_SSR(sbi) && get_ssr_segment(sbi, type))
> change_curseg(sbi, type, true);
> else
> --
> 1.8.5.2
prev parent reply other threads:[~2017-02-25 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 10:06 [PATCH] f2fs: change the codes of checking CP_CRC_RECOVERY_FLAG to macro Yunlong Song
2017-02-24 10:29 ` Chao Yu
2017-02-24 11:11 ` Yunlong Song
2017-02-24 11:37 ` Chao Yu
2017-02-24 11:57 ` Yunlong Song
2017-02-24 18:12 ` Jaegeuk Kim
2017-02-25 0:54 ` Chao Yu
2017-02-25 8:10 ` Yunlong Song
2017-02-25 8:01 ` [PATCH v2] " Yunlong Song
2017-02-25 18:46 ` Jaegeuk Kim [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=20170225184619.GC51627@jaegeuk.local \
--to=jaegeuk@kernel.org \
--cc=bintian.wang@huawei.com \
--cc=chao@kernel.org \
--cc=cm224.lee@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=sylinux@163.com \
--cc=yuchao0@huawei.com \
--cc=yunlong.song@huawei.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