From: Chao Yu <yuchao0@huawei.com>
To: Robin Hsu <robinh3123@gmail.com>,
<linux-f2fs-devel@lists.sourceforge.net>, <jaegeuk@kernel.org>,
<chao@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v3 2/3] f2fs-tools:sload.f2fs compression support
Date: Thu, 10 Dec 2020 16:42:51 +0800 [thread overview]
Message-ID: <785e9f0a-c3d6-9cc5-f17a-a3cc58a43a0f@huawei.com> (raw)
In-Reply-To: <20201208081555.652932-3-robinh3123@gmail.com>
On 2020/12/8 16:15, Robin Hsu wrote:
> From: Robin Hsu <robinhsu@google.com>
>
> Add F2FS compression support for sload
> * Support file extension filter, either default-accept or default-deny
> policy
> * Support choice of compression algorithm, LZO (version 2) or LZ4
> (default)
> * Support custom log of cluster size
> * Support minimum number of compressed blocks per cluster (default 1).
> A cluster will not be compressed if the number can not be met.
> * suuport -r (read-only) option
Could you please update manual as well?
> +
> + /* sldc: sload compression support */
Personally, I don't like the naming method of adding "sldc_" prefix... :(
> + bool sldc_en;
> + bool sldc_use_allow_list; /* default false to use the deny list */
> + struct compress_ctx sldc_cc;
> + u8 sldc_ca; /* compress algorithm: 0 = LZO, 1 = LZ4 */
> + compress_ops *sldc_compr;
> + enum filter_policy sldc_policy;
> + /* max_cppc can used to specify minimum compression rate */
> + unsigned int sldc_min_cbpc; /* min compressed pages per cluster */
> + bool sldc_got_opt;
> + bool sldc_immutable;
> + struct ext_tbl_op *sldc_ef; /* extension filter */
The variables name like sldc_en, sldc_ca, min_cbpc, sldc_ef makes developers
hard to understand w/o comments, and also there is no comments for several
variable like sldc_en, sldc_cc...
Could you please improve the naming like f2fs-tools style?
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-12-10 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 8:15 [f2fs-dev] [PATCH v3 0/3] f2fs-tools: sload compression support Robin Hsu
2020-12-08 8:15 ` [f2fs-dev] [PATCH v3 1/3] f2fs-tools: Added #ifdef WITH_func Robin Hsu
2020-12-10 8:41 ` Chao Yu
2020-12-08 8:15 ` [f2fs-dev] [PATCH v3 2/3] f2fs-tools:sload.f2fs compression support Robin Hsu
2020-12-08 20:18 ` Jaegeuk Kim
2020-12-10 8:42 ` Chao Yu [this message]
[not found] ` <CAKnFrsLmEROi+ZwVCmoC=W7u+rVoZfWGC9Lr9_y=oLMUZMw63Q@mail.gmail.com>
2020-12-10 16:22 ` Jaegeuk Kim
2020-12-10 16:36 ` Jaegeuk Kim
2020-12-18 11:29 ` Satya Tangirala via Linux-f2fs-devel
2020-12-18 16:18 ` Jaegeuk Kim
2020-12-08 8:15 ` [f2fs-dev] [PATCH v3 3/3] f2fs-tools:sload.f2fs compress: Fixed automake Robin Hsu
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=785e9f0a-c3d6-9cc5-f17a-a3cc58a43a0f@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=robinh3123@gmail.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).