From: Ju Hyung Park <qkrwngud825@gmail.com>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] f2fs: dirty memory increasing during gc_urgent
Date: Sun, 25 Aug 2019 20:06:52 +0900 [thread overview]
Message-ID: <CAD14+f1vkJtPpUEU1MJbxkZRRjR5Jqa8WWAGKBb2Xw4pPS3WRg@mail.gmail.com> (raw)
In-Reply-To: <baa8b0ce-99b4-4f74-ff7d-e204bced4168@kernel.org>
Hi Chao,
On Sat, Aug 24, 2019 at 12:52 AM Chao Yu <chao@kernel.org> wrote:
> It's not intentional, I failed to reproduce this issue, could you add some logs
> to track why we stop urgent GC even there are still dirty segments?
I'm pretty sure you can reproduce this issue quite easily.
I can see this happening on multiple devices including my workstation,
laptop and my Android phone.
Here's a simple reproduction step:
1. Do `rm -rf * && git reset --hard` a few times under a Linux kernel Git
2. Do a sync
3. echo 1 > /sys/fs/f2fs/dev/gc_urgent_sleep_time
4. echo 1 > /sys/fs/f2fs/dev/gc_urgent
5. Once the number on "GC calls" doesn't change, look at "Dirty" under
/sys/kernel/debug/f2fs/status. It's close to 0.
6. After doing a 'sync', "Dirty" increases a lot.
7. Remember the number on "GC calls" and run 3 and 4 again.
8. The number of "GC calls" increases by a few hundreds.
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:[~2019-08-25 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 14:15 [f2fs-dev] f2fs: dirty memory increasing during gc_urgent Ju Hyung Park
2019-08-15 6:48 ` Chao Yu
2019-08-16 15:37 ` Ju Hyung Park
2019-08-23 15:52 ` Chao Yu
2019-08-25 11:06 ` Ju Hyung Park [this message]
2019-08-26 7:17 ` 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=CAD14+f1vkJtPpUEU1MJbxkZRRjR5Jqa8WWAGKBb2Xw4pPS3WRg@mail.gmail.com \
--to=qkrwngud825@gmail.com \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).