From: Chao Yu <yuchao0@huawei.com>
To: Park Ju Hyung <qkrwngud825@gmail.com>,
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH 1/2] mkfs.f2fs: add "zip" to cold data types
Date: Wed, 14 Aug 2019 09:53:26 +0800 [thread overview]
Message-ID: <eff187a3-27a8-f5d1-c667-26f9e7b384d8@huawei.com> (raw)
In-Reply-To: <c5fbcb16-c7b2-988d-2110-8ce53a6137f6@huawei.com>
On 2019/8/14 9:47, Chao Yu wrote:
> Hi Ju Hyung,
>
> On 2019/8/13 6:52, Park Ju Hyung wrote:
>> A lot of Linux users have big, cold "zip" files.
>
> In android, as I see, most zip file is small-sized log type, and will be removed
> after a roll-back, such as:
>
> time1: create log1.zip
> time2: create log2.zip
> time3: create log3.zip
> time4: remove log1.zip, rename log2.zip -> log1.zip; rename log3.zip ->
> log2.zip; create log3.zip
>
> I suggest we can keep zip type in android as warm type with IPU mode to avoid
> fragmentation caused by small holes in cold area. In linux distro, I agreed to
> treat zip as cold type.
>
> So what about configuring zip type in f2fs_init_configuration() under '#ifndef
It seems it doesn't have to configure this in f2fs_init_configuration(), just
adding #ifndef WITH_ANDROID will be fine.
> WITH_ANDROID'?
>
> What do you think?
>
> Thanks,
>
>>
>> Signed-off-by: Park Ju Hyung <qkrwngud825@gmail.com>
>> ---
>> mkfs/f2fs_format.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/mkfs/f2fs_format.c b/mkfs/f2fs_format.c
>> index 9402619..37d82c3 100644
>> --- a/mkfs/f2fs_format.c
>> +++ b/mkfs/f2fs_format.c
>> @@ -66,6 +66,7 @@ const char *media_ext_lists[] = {
>> "webp",
>>
>> /* archives */
>> + "zip",
>> "jar",
>> "deb",
>> "iso",
>>
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> .
>
_______________________________________________
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:[~2019-08-14 1:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 22:52 [f2fs-dev] [PATCH 1/2] mkfs.f2fs: add "zip" to cold data types Park Ju Hyung
2019-08-12 22:52 ` [f2fs-dev] [PATCH 2/2] mkfs.f2fs: add VM disk files to hot " Park Ju Hyung
2019-08-14 1:51 ` Chao Yu
2019-08-14 9:22 ` Ju Hyung Park
2019-08-15 6:23 ` Chao Yu
2019-08-14 1:47 ` [f2fs-dev] [PATCH 1/2] mkfs.f2fs: add "zip" to cold " Chao Yu
2019-08-14 1:53 ` Chao Yu [this message]
2019-08-14 9:20 ` Ju Hyung Park
2019-08-14 9:47 ` Chao Yu
2019-08-14 14:10 ` Ju Hyung Park
2019-08-15 3:04 ` 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=eff187a3-27a8-f5d1-c667-26f9e7b384d8@huawei.com \
--to=yuchao0@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=qkrwngud825@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).