From: Artem Bityutskiy <dedekind1@gmail.com>
To: Atlant Schmidt <aschmidt@dekaresearch.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: Can major re-organization activities of the UBIfs be "deliberately provoked"?
Date: Fri, 22 Jul 2011 11:34:02 +0300 [thread overview]
Message-ID: <1311323646.20707.18.camel@sauron> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD32A7208F97E@dekaexchange07.deka.local>
On Thu, 2011-07-21 at 09:33 -0400, Atlant Schmidt wrote:
> Folks:
>
> We're using the UBIfs with our realtime equipment. We've
> noticed a behavior where, every so often, the flush-ubifs
> thread demands very, very large amounts of CPU time, blocking
> all of our other processes that use the Linux time-sliced
> scheduler. These bursts come at arbitrary intervals but
> commonly last ten to fifteen seconds.
If the bursts are probably dues to write-back which is initiated by VFS.
When UBIFS is doing write-back it needs to compress data, it may need to
do GC if there is not space.
First - check if the bursts are indeed about write-back - change the
period of write-back and see. Or type sync and see the utilization. Then
you can play with VFS knobs and lessen the write-back intervals
in /proc.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2011-07-22 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 13:33 Can major re-organization activities of the UBIfs be "deliberately provoked"? Atlant Schmidt
2011-07-22 8:34 ` Artem Bityutskiy [this message]
2011-07-22 10:50 ` Atlant Schmidt
2011-07-22 10:59 ` Artem Bityutskiy
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=1311323646.20707.18.camel@sauron \
--to=dedekind1@gmail.com \
--cc=aschmidt@dekaresearch.com \
--cc=linux-mtd@lists.infradead.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