From: "Jon Burford" <jburford@xsilogy.com>
To: <mtd@infradead.org>
Subject: IGEL DOC2000 flash driver performance
Date: Tue, 9 Nov 1999 17:02:29 -0800 [thread overview]
Message-ID: <00e901bf2b17$42a84770$6600160a@isidesign.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
I have been using the IGEL flash driver on a Linux 2.2.12 system now for several months. One very annoying "feature" is that it causes the entire OS to hang for 2-5 seconds after mounting or moderate write operations. I talked with an M-Systems tech and although they did not write the driver, he thought it might be due to the garbage collection running in the DOC2000 firmware. When a block becomes some configurable percentage utilized, the garbage collector tries to coallesce the used portion of this block with others to decrease block fragmentation and increase wearability. His theory was that the driver would request space for a particular write operation and if garbage collection was necessary, the write operation would block. My problem is that when this happens and the blocking lasts for > 1.5 seconds, my watchdog refresh process can't pet the watchdog and the system resets. I have tried making the watchdog process a real-time thread with RTLinux, but the RTLinux beta11 is proving to be a little unstable for my blood right now. I am wondering if anyone has encountered this problem and/or may have some advice for me. Does the MTD DOC2000 driver suffer from this behavior and can it be patched into a 2.2.12 kernel? Any other thoughts?
TIA!
Regards,
Jon
[-- Attachment #2: Type: text/html, Size: 1845 bytes --]
next reply other threads:[~1999-11-10 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-10 1:02 Jon Burford [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-11-10 8:42 IGEL DOC2000 flash driver performance David Woodhouse
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='00e901bf2b17$42a84770$6600160a@isidesign.com' \
--to=jburford@xsilogy.com \
--cc=mtd@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