From: Jon Ringle <jon@ringle.org>
To: "Jörn Engel" <joern@lazybastard.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [SPAM] Re: P30 flash left in read status mode after a write
Date: Wed, 14 Feb 2007 16:22:30 -0500 [thread overview]
Message-ID: <45D37D96.4010501@ringle.org> (raw)
In-Reply-To: <20070214205601.GB20486@lazybastard.org>
Jörn Engel wrote:
> On Wed, 14 February 2007 13:52:31 -0500, Jon Ringle wrote:
>
>> This did indeed seem to fix the problem, but I'm not sure if I might
>> inadvertently be causing some side effect. I believe that I might be
>> taking a slight performance hit to consecutive jffs2 write operations
>> because now each write operation will need to spend more cycles putting
>> the flash in to a write mode.
>>
>
> If the performance hit concerns you, you could set a timer instead of
> changing the chip state. Only if the timer expires - which means that
> consecutive writes are a non-issue - do you change the chip state.
>
>
Using a timer sounds like a good idea. I'll keep it in mind. I'm not
sure yet whether I'm concerned about the performance hit as I haven't
profiled the impact yet. Has anyone got any data that shows what kind of
improvement jffs2 write operations get with this optimization in place
to leave flash in read status mode?
Jon
next prev parent reply other threads:[~2007-02-14 21:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 18:52 P30 flash left in read status mode after a write Jon Ringle
2007-02-14 19:14 ` Josh Boyer
2007-02-14 19:47 ` Nicolas Pitre
2007-02-14 20:09 ` [SPAM] " Jon Ringle
2007-02-14 20:33 ` Nicolas Pitre
2007-02-14 20:41 ` Jon Ringle
2007-02-14 20:57 ` Nicolas Pitre
2007-02-14 20:56 ` Jörn Engel
2007-02-14 21:22 ` Jon Ringle [this message]
2007-02-14 21:34 ` [SPAM] " Nicolas Pitre
2007-02-20 19:11 ` Alexey Korolev
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=45D37D96.4010501@ringle.org \
--to=jon@ringle.org \
--cc=joern@lazybastard.org \
--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