From: Daniel Walker <danielwa@cisco.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Nikunj Kela (nkela)" <nkela@cisco.com>,
Richard Weinberger <richard.weinberger@gmail.com>,
"linux-mtd @ lists . infradead . org"
<linux-mtd@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>
Subject: Re: [PATCH] jffs2: implement mount option to configure endianness
Date: Mon, 12 Nov 2018 16:06:27 -0800 [thread overview]
Message-ID: <20181113000627.oe7cshgzfk4lf3to@zorba> (raw)
In-Reply-To: <b797e897960c3c047dfc7874615358a5443038a8.camel@infradead.org>
On Mon, Nov 12, 2018 at 03:43:37PM -0800, David Woodhouse wrote:
>
> That can't hurt. We should probably look at the time elapsed before you
> can *write* to it (when the background scan and crc checking is
> complete) rather than just reading.
>
I'm not sure how to test that, but I tried this,
mount -t jffs2 mtd7 /mnt ; perf stat -B dd if=/dev/zero of=/mnt/test bs
1 count=1;
What would you suggest for testing this ?
Daniel
next prev parent reply other threads:[~2018-11-13 0:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 21:49 [PATCH] jffs2: implement mount option to configure endianness Nikunj Kela
2018-11-07 9:05 ` David Woodhouse
2018-11-07 9:16 ` Joakim Tjernlund
2018-11-07 16:12 ` David Woodhouse
2018-11-07 17:33 ` Daniel Walker
2018-11-07 17:58 ` David Woodhouse
2018-11-07 18:41 ` Joakim Tjernlund
2018-11-08 15:25 ` Christoph Hellwig
2018-11-07 19:21 ` Daniel Walker
2018-11-07 18:04 ` Nikunj Kela (nkela)
2018-11-07 18:14 ` Richard Weinberger
2018-11-08 8:11 ` David Woodhouse
2018-11-08 18:01 ` Nikunj Kela (nkela)
2018-11-08 18:50 ` Joakim Tjernlund
2018-11-08 19:47 ` David Woodhouse
2018-11-12 21:43 ` Daniel Walker
2018-11-12 22:50 ` Daniel Walker
2018-11-12 23:11 ` David Woodhouse
2018-11-12 23:40 ` Daniel Walker
2018-11-12 23:43 ` David Woodhouse
2018-11-13 0:06 ` Daniel Walker [this message]
2018-11-13 21:01 ` Daniel Walker
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=20181113000627.oe7cshgzfk4lf3to@zorba \
--to=danielwa@cisco.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nkela@cisco.com \
--cc=richard.weinberger@gmail.com \
--cc=xe-linux-external@cisco.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 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.