From: Ju Hyung Park <qkrwngud825@gmail.com>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] f2fs: dirty memory increasing during gc_urgent
Date: Wed, 14 Aug 2019 23:15:09 +0900 [thread overview]
Message-ID: <CAD14+f1YGinNQuVKc371vgJGJaaqYWqcaP6WwSuP1mwf-D2Tzw@mail.gmail.com> (raw)
Hi.
I'm reporting some strangeness with gc_urgent.
When running gc_urgent, I can see that dirty memory written in
/proc/meminfo continuously getting increased until GC cannot find any
more segments to clean.
I thought FG_GC are flushed.
And after GC ends, if I do `sync` and run gc_urgent again, it easily
runs thousands of times more.
Is this an expected behavior?
I would much prefer gc_urgent cleaning everything up at first run,
without having to sync at the end and running gc_urgent again.
Thanks.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2019-08-14 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 14:15 Ju Hyung Park [this message]
2019-08-15 6:48 ` [f2fs-dev] f2fs: dirty memory increasing during gc_urgent 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
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+f1YGinNQuVKc371vgJGJaaqYWqcaP6WwSuP1mwf-D2Tzw@mail.gmail.com \
--to=qkrwngud825@gmail.com \
--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).