From: David Wagner <david.wagner@free-electrons.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
tim.bird@am.sony.com
Subject: Re: Flash filesystems benchmarks
Date: Thu, 28 Jul 2011 22:05:46 +0200 [thread overview]
Message-ID: <4E31C11A.8050105@free-electrons.com> (raw)
In-Reply-To: <CAAfyv35zgDLpf6Hs0G0wESh0-BjoiWMH+4wA7+anSwR0rREtbA@mail.gmail.com>
Hi,
On 28/07/2011 21:14, Belisko Marek wrote:
> Hi,
> Great job ;). Maybe small README how to use scripts. I try to run
> ./performance-test.py but got en error because test.cfg doesn't exist.
> Shouldn't there be input argument for specific board something like:
> [...]
Thanks for the feedback. You're right, READMEs are missing ; they'll come.
The current procedure, regarding the configuration file, is:
* write a configuration file (like those already provided as examples)
* cp it to test.cfg
* launch performance-test.py
why the cp ? because it allows to tweak it without changing the original.
But it would certainly be best to use a proper argument parsing
(argparse, like for gnuplotize_*.py and generate_graphs.py) and have an
optional configuration file.
The material and documentation to reproduce the tests isn't fully
available yet but will be very soon. I can already give you a link to
the debian root filesystem (to be exported through NFS) that was used ;
however I can't guarantee yet that it will work.
http://free-electrons.com/~david/pub/RFS-benchmarks.tar.lzma (1.1GB)
David.
--
David Wagner, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-07-28 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 9:53 Flash filesystems benchmarks David Wagner
2011-07-28 19:14 ` Belisko Marek
2011-07-28 20:05 ` David Wagner [this message]
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=4E31C11A.8050105@free-electrons.com \
--to=david.wagner@free-electrons.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.belisko@gmail.com \
--cc=tim.bird@am.sony.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).