From: Artem Bityutskiy <dedekind1@gmail.com>
To: "N. van Bolhuis" <nvbolhuis@aimvalley.nl>
Cc: linux-mtd@lists.infradead.org, joakim.tjernlund@transmode.se
Subject: Re: a UBIFS image makes task pdflush blocked > 120 seconds
Date: Tue, 17 Nov 2009 10:25:18 +0200 [thread overview]
Message-ID: <1258446318.27437.60.camel@localhost> (raw)
In-Reply-To: <4B012D0D.4080500@aimvalley.nl>
On Mon, 2009-11-16 at 11:44 +0100, N. van Bolhuis wrote:
> > The only way to help from UBI side I see is to lessen the UBI background
> > thread's priority - you could try this. Or for the background
> > formatting, have a 'yield()' call in the UBI background thread.
> >
> > Or we could have a 'nor_erase_quirk()' in the UBI background thread,
> > which would call yield() if the previous operation was "erase", and the
> > next one is also "erase". You could try this.
> >
> > Do you have any other suggestions?
>
> No. Let's try the 'nor_erase_quirk()' solution.
Thinking about this more, I do not like using 'yield()'. JFFS2 had it in
the background thread, and there were many discussions about this, it
hurt one group of people, and helps another group. But it is hacky,
because depending on kernel version, 'yield()' may have different
effects. I do not like it.
Could you just try lowering the UBI bgt priority, and see if it helps?
I would not want to go for any yielding unless you report it does not
help.
Just renice the BGT and see what happens, and report back please.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-11-17 8:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B012D0D.4080500@aimvalley.nl>
2009-11-16 12:12 ` a UBIFS image makes task pdflush blocked > 120 seconds Joakim Tjernlund
2009-11-17 8:25 ` Artem Bityutskiy [this message]
2009-11-17 16:25 ` Norbert van Bolhuis
2009-11-18 8:28 ` Artem Bityutskiy
2009-11-18 9:26 ` Norbert van Bolhuis
2009-11-18 9:40 ` Artem Bityutskiy
2009-11-18 10:38 ` Joakim Tjernlund
2009-11-18 10:54 ` Artem Bityutskiy
2009-11-18 10:59 ` Norbert van Bolhuis
2009-11-18 11:01 ` Joakim Tjernlund
[not found] <34637.10.10.0.184.1258202287.squirrel@intranet.aimsys.nl>
2009-11-16 8:13 ` Artem Bityutskiy
2009-11-16 8:53 ` Joakim Tjernlund
2009-11-16 23:22 ` Jamie Lokier
2009-11-17 8:31 ` Joakim Tjernlund
2009-11-17 10:45 ` Norbert van Bolhuis
2009-10-09 13:02 Norbert van Bolhuis
2009-10-11 13:52 ` Artem Bityutskiy
2009-10-12 10:09 ` Norbert van Bolhuis
2009-10-14 8:56 ` Artem Bityutskiy
2009-11-11 15:54 ` Norbert van Bolhuis
2009-11-13 8:20 ` Artem Bityutskiy
2009-11-13 15:09 ` Norbert van Bolhuis
2009-11-13 15:52 ` Artem Bityutskiy
2009-11-13 15:56 ` Artem Bityutskiy
2009-11-13 16:28 ` Joakim Tjernlund
2009-10-11 14:04 ` Artem Bityutskiy
2009-10-11 14:09 ` 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=1258446318.27437.60.camel@localhost \
--to=dedekind1@gmail.com \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-mtd@lists.infradead.org \
--cc=nvbolhuis@aimvalley.nl \
/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