linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Ju Hyung Park <qkrwngud825@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] mkfs.f2fs: add "zip" to cold data types
Date: Thu, 15 Aug 2019 11:04:15 +0800	[thread overview]
Message-ID: <a8f420d3-178b-9200-b4a6-cccf11c420db@huawei.com> (raw)
In-Reply-To: <CAD14+f0PkiuFkg04eGVJQkeeG+JjFdas6hWCc_FazGK5VQh0KA@mail.gmail.com>

Hi Ju Hyung,

On 2019/8/14 22:10, Ju Hyung Park wrote:
> Hi Chao,
> 
> /data/log isn't even here.
> I think it must be specific to EMUI.

Alright, at least in EMUI, it looks not proper to me to set cold flag on zip
file according to result of hot/cold separation investigation recently.

IMO, it will be more common to store large stable zip/rar file in Linux
desktop/server or Window OS...

Thanks,

> 
> Thanks.
> 
> On Wed, Aug 14, 2019 at 6:48 PM Chao Yu <yuchao0@huawei.com> wrote:
>>
>> Hi Ju Hyung,
>>
>> On 2019/8/14 17:20, Ju Hyung Park wrote:
>>> Hi Chao,
>>>
>>> On Wed, Aug 14, 2019 at 10:47 AM Chao Yu <yuchao0@huawei.com> wrote:
>>>> 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.
>>>
>>> I actually thought your original suggestion of adding "zip" was to
>>> handle big zip files under /sdcard(/data/media).
>>>
>>> The one case you've mentioned will be entirely dependent on which apps
>>> user's using.
>>
>> Yeah, actually, now I didn't see much large zip file in my external storage,
>> most of them are xxxKB or xMB, some of them looks very old tho. :)
>>
>>> In case of mine, I don't have any zip files under /data that's
>>> seemingly used for logs.
>>
>> Huawei cell phone has log file with .zip/.gz type locating in /data/log/... can
>> you search that directory?
>>
>> If we relocate them into cold area, they will make holes in cold area crazily,
>> as they have small size and will be created/unlinked frequently.
>>
>> Thanks,
>>
>>>
>>> Thanks,
>>> .
>>>
> .
> 


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2019-08-15  3:04 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
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 [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=a8f420d3-178b-9200-b4a6-cccf11c420db@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).