From: Bernhard Priewasser <priewasser@gmail.com>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: Strange NOR read/write throughput behaviour
Date: Tue, 22 Nov 2005 11:14:00 +0100 [thread overview]
Message-ID: <4382EF68.3010204@gmail.com> (raw)
In-Reply-To: <6934efce0511211418s5317b7a6tee5b391e28eb8491@mail.gmail.com>
> What about the read test.
As simple as you can imagine. Write a file (fopen, fwrite, fclose), wait
some time, read the file (fopen, fread, fclose).
Do you think there are caching mechanism responsible for it?
--
Bernhard
next prev parent reply other threads:[~2005-11-22 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 10:27 Strange NOR read/write throughput behaviour Bernhard Priewasser
2005-11-17 17:58 ` Jared Hulbert
2005-11-18 9:31 ` Bernhard Priewasser
2005-11-21 22:18 ` Jared Hulbert
2005-11-22 10:14 ` Bernhard Priewasser [this message]
2005-12-03 21:36 ` Jared Hulbert
2005-12-06 12:14 ` Bernhard Priewasser
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=4382EF68.3010204@gmail.com \
--to=priewasser@gmail.com \
--cc=jaredeh@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.