From: Kevin Vigor <kevin@realmsys.com>
To: ghannon@cspi.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] avoid unnnecessary mtd read when read can be satisfied by write buffer
Date: Thu, 01 Jun 2006 10:10:34 -0600 [thread overview]
Message-ID: <447F117A.7070708@realmsys.com> (raw)
In-Reply-To: <85257180.00537972.00@pine.cspi.com>
ghannon@cspi.com wrote:
>However when programming a flash device and then reading back
>to verify that it was programmed correctly, I think this write
>cache would defeat the purpose.
>
>
>
This problem already exists with the wbuf code since a call to
jffs2_flash_read will return the write buffer contents regardless of the
actual contents of the media (unless you call jffs2_flush_wbuf_pad()
between the write and the read).
So the semantics could remain the same in that an explicit flush would
be necessary in order to validate the data on flash.
next parent reply other threads:[~2006-06-01 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85257180.00537972.00@pine.cspi.com>
2006-06-01 16:10 ` Kevin Vigor [this message]
2006-05-31 21:50 [PATCH] avoid unnnecessary mtd read when read can be satisfied by write buffer Kevin Vigor
2006-06-01 14:32 ` Jörn Engel
2006-06-01 14:39 ` David Woodhouse
2006-06-01 14:49 ` Jörn Engel
2006-06-01 15:05 ` David Woodhouse
2006-06-01 15:27 ` Jörn Engel
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=447F117A.7070708@realmsys.com \
--to=kevin@realmsys.com \
--cc=ghannon@cspi.com \
--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