From: Bart Veer <bartv@ecoscentric.com>
To: zankl@decomsys.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] JFFS2 Access and interrupts
Date: Thu, 14 Sep 2006 15:15:00 -0000 [thread overview]
Message-ID: <pnac52h436.fsf@delenn.bartv.net> (raw)
In-Reply-To: <0F0005CE495E094A96B04D78F24E5A7F3858B5@mana.decomsys.com> (zankl@decomsys.com)
>>>>> "Gernot" == Gernot Zankl <zankl@decomsys.com> writes:
>> > FYI I finally found the/our bug, causing the application to
>> > corrupt the jffs2. We just used the wrong block size in
>> > the configuration of the underlying flash driver, causing to
>> > erase too much flash memory (and destroying still active inodes).
>>
>> FAOD - it had *nothing* to do with interrupts during FLASH operations?
Gernot> At least not in "our" version of the flash driver (v1)
Gernot> which has been provided and modified by Analogue&Micro,
Gernot> where all calls to the critical functions are guarded by
Gernot> the HAL_DISABLE_INTERRUPTS and HAL_RESTORES_INTERRUPTS
Gernot> macros.
Of course that approach gives you an interrupt latency of somewhere
from several 100 milliseconds up to 5 seconds, depending on the exact
flash hardware and the environmental conditions. That is the time
needed to erase a whole flash sector. So any time you perform jffs2
file I/O your application may become completely unresponsive to all
external events for a number of seconds. It depends on the application
whether or not such behaviour is acceptable.
Bart
--
Bart Veer eCos Configuration Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-09-14 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 10:36 [ECOS] Getting segmentation fault while unmounting JFFS2 file system Amitesh Singh
2006-09-06 10:50 ` Gary Thomas
2006-09-06 16:43 ` [ECOS] JFFS2 Access and interrupts Gernot Zankl
2006-09-06 19:32 ` Gary Thomas
2006-09-07 14:50 ` Bart Veer
2006-09-08 8:43 ` Andrew Lunn
2006-09-08 10:00 ` Gernot Zankl
2006-09-08 16:58 ` Andrew Lunn
2006-09-14 12:27 ` Gernot Zankl
2006-09-14 12:31 ` Gary Thomas
2006-09-14 12:42 ` Gernot Zankl
2006-09-14 12:56 ` Gary Thomas
2006-09-14 15:15 ` Bart Veer [this message]
2006-09-07 11:21 Zimman, Chris
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=pnac52h436.fsf@delenn.bartv.net \
--to=bartv@ecoscentric.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=zankl@decomsys.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).