From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>,
Wang Fangpeng <wangfangpeng1@huawei.com>,
linux-mtd@lists.infradead.org
Subject: Re: Question: background GC on UBIFS
Date: Thu, 31 Mar 2016 12:50:15 +0300 [thread overview]
Message-ID: <1459417815.6224.11.camel@gmail.com> (raw)
In-Reply-To: <56FCE58E.3060200@nod.at>
On Thu, 2016-03-31 at 10:53 +0200, Richard Weinberger wrote:
> Doing it periodically is doable but how often and when? Only when the
> system
> is completely idle?
I would say - we should give a knob (mechanism) and let the userland
decide when and how much to run it (policy).
> But you can give it a try. Add a new debugfs file to trigger an
> aggressive GC run.
I'd say the trigger should be - GC one eraseblock. Or better, clean
some dirt, or make some free space. Internally this will be GC one
eraseblock, but later on this may change. UBIFS will pick the best
eraseblock to GC automatically. Userland just triggers it at the right
poing. I guess this should be a blocking API - userland blocks until GC
is done. Then it can force more GC.
You can play with this knob, see if it helps.
However, fundamentally, UBIFS will always get slower when the space is
short, by its design. You can make it a bit faster when you have little
space, but you can't make it as fast as when there is more space,
unfortunately. Not easily, at least.
Artem.
prev parent reply other threads:[~2016-03-31 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 6:25 Question: background GC on UBIFS Wang Fangpeng
2016-03-31 8:53 ` Richard Weinberger
2016-03-31 9:50 ` Artem Bityutskiy [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=1459417815.6224.11.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=wangfangpeng1@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.