From: Chao Yu <yuchao0@huawei.com>
To: lampahome <pahome.chen@mirlab.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Can I know if now is gc-ing or checkpointing?
Date: Mon, 6 Jul 2020 18:27:21 +0800 [thread overview]
Message-ID: <7dafaedf-1efa-6e78-f3c4-fea93f4045a9@huawei.com> (raw)
In-Reply-To: <CAB3eZfumC+gx2ccnhOqG7ZLx+6bd0VLuBOS6G2WNqz843vC_+A@mail.gmail.com>
On 2020/7/6 16:58, lampahome wrote:
> Chao Yu <yuchao0@huawei.com> 於 2020年7月6日 週一 下午4:51寫道：
>>
>> On 2020/7/6 16:11, lampahome wrote:
>>> Brief procedures:
>>> parted /dev/sdd1 as 160GB disk
>>> mkfs -t f2fs /dev/sdd1
>>> mount /dev/sdd1 /mnt/f2fsdir
>>>
>>> I use shell script to create 20 fio concurrently and wait for finish.
>>> fio command:
>>> fio -bs=4k -iodepth=4 -rw=write -ioengine=libaio -name=my -direct=0
>>
>> Why not using direct=1 combining with libaio? otherwise data was only
>> written to cache.
>>
> So directIO help performance?
I guess libaio + directio shows real device performance, rather than memory
performance when using libaio + bufferedio if your memory is large enough...
>
>> Below info shows GC or CP didn't affect the test result.
> Why? So the GC and CP works normally?
> Could you tell me in detail? thanks
The GC and CP value is very small, I don't think that could affect performance.
> .
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2020-07-06 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 7:10 [f2fs-dev] Can I know if now is gc-ing or checkpointing? lampahome
2020-07-06 7:29 ` Chao Yu
2020-07-06 7:34 ` lampahome
2020-07-06 7:46 ` Chao Yu
2020-07-06 8:11 ` lampahome
2020-07-06 8:51 ` Chao Yu
2020-07-06 8:58 ` lampahome
2020-07-06 10:27 ` 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=7dafaedf-1efa-6e78-f3c4-fea93f4045a9@huawei.com \
--to=yuchao0@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=pahome.chen@mirlab.org \
/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).