From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: linux-mtd@lists.infradead.org, "Albrecht,
Harald" <harald.albrecht@elreha.de>
Subject: Re: JFFS2 Garbage collection issue
Date: Wed, 27 Nov 2013 20:34:06 +0100 [thread overview]
Message-ID: <1385580846.2836.1@deneb.(none)> (raw)
In-Reply-To: <OFC2D68B7C.CF5FC776-ONC1257C30.00395D40-C1257C30.0039B49A@transmode.se> (from joakim.tjernlund@transmode.se on Wed Nov 27 11:30:18 2013)
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
Hi Jocke:
Am 27.11.13 11:30 schrieb(en) Joakim Tjernlund:
> BTW, I guess you got logging to file such as syslog on your system? JFFS2 really don't do well with small incremental writes. I recommend you turn such logging off.
Does the delay by the gc process happen only when the jffs2 fs is mounted, or also during the normal operation when many updates occur?
Background: I had a similar issue as Harald with a NVRAM which is used to hold quickly changing event buffers and logs. My solution was to wait for the gc process during the startup of the system, before the "main" application is launched. However, if this could also happen *after* the initial scan has finished, this would be bad news for me, as I then probably would need the SIG(STOP|CONT) approach...
Thanks,
Albrecht.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2013-11-27 19:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 10:11 JFFS2 Garbage collection issue Albrecht, Harald
2013-11-27 10:23 ` Joakim Tjernlund
2013-11-27 10:30 ` Joakim Tjernlund
2013-11-27 19:34 ` Albrecht Dreß [this message]
2013-11-28 6:33 ` Joakim Tjernlund
2013-11-28 9:33 ` Albrecht, Harald
2013-11-28 11:03 ` Joakim Tjernlund
2013-11-27 19:27 ` Albrecht Dreß
-- strict thread matches above, loose matches on Subject: below --
2008-07-27 18:44 JFFS2 Garbage Collection Issue suresh
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='1385580846.2836.1@deneb.(none)' \
--to=albrecht.dress@arcor.de \
--cc=harald.albrecht@elreha.de \
--cc=joakim.tjernlund@transmode.se \
--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