From: Fengnan Chang <fengnanchang@gmail.com>
To: yuchao0@huawei.com
Cc: jaegeuk@kernel.org, changfengnan@vivo.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] =?y?q?Re=3A=20=5Bf2fs-dev=5D=20=E7=AD=94=E5=A4=8D=3A=20=20=5BRFC=20PATCH=5D=20f2fs=3A=20add=20no=20compress=20extensions=20support?=
Date: Sat, 17 Apr 2021 15:02:51 +0800 [thread overview]
Message-ID: <20210417070251.42979-1-fengnanchang@gmail.com> (raw)
In-Reply-To: <4dc282e0-b41c-caf2-c2ff-a6372e60a906@huawei.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 794 bytes --]
In this patch, we cannot handle files without extensions. At the moment there is just a rough idea，test a portion of the data to decide whether to compress it before performing a full compression. It may need more test. Any other suggestions?
In my consider, the non-compress flag has a higher priority than the compressed flag.
1. the same extension name cannot not appear in both compress and non-compress extension at the same time， check this in mount process.
2. If the compress extension specifies all files, the types specified by the non-compress extension will be treated as special cases and will not be compressed.
3. If the non-compress extension specifies all files, should not specifies any compress extension, check in mount process too.
Any other suggestions?
Thanks.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 179 bytes --]
_______________________________________________
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:[~2021-04-17 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 9:47 [f2fs-dev] [RFC PATCH] f2fs: add no compress extensions support Fengnan Chang
2021-04-15 1:31 ` Chao Yu
2021-04-15 1:56 ` [f2fs-dev] 答复: " changfengnan
2021-04-17 2:43 ` Chao Yu
2021-04-17 7:02 ` Fengnan Chang [this message]
2021-04-19 16:22 ` Jaegeuk Kim
2021-04-20 2:08 ` [f2fs-dev] 答复: " changfengnan
2021-04-21 13:06 ` changfengnan
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=20210417070251.42979-1-fengnanchang@gmail.com \
--to=fengnanchang@gmail.com \
--cc=changfengnan@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@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;
as well as URLs for NNTP newsgroup(s).