From: Artem Bityutskiy <dedekind1@gmail.com>
To: David Wuertele <dave+gmane@wuertele.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Performance effect of mounting jffs2 via mtdblock
Date: Thu, 08 Jul 2010 12:11:52 +0300 [thread overview]
Message-ID: <1278580312.12733.75.camel@localhost> (raw)
In-Reply-To: <loom.20100623T212106-800@post.gmane.org>
On Wed, 2010-06-23 at 19:26 +0000, David Wuertele wrote:
> Reading http://www.linux-mtd.infradead.org/faq/jffs2.html, it says that jffs2
> can be mounted with or without the mtdblock driver. Eg:
>
> mount -t jffs2 mtd2 /foo
> vs
> mount -t jffs2 /dev/mtdblock2 /foo
>
> I'm wondering what is the difference between these two methods with respect to
> performance?
There is no difference.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-07-08 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 19:26 Performance effect of mounting jffs2 via mtdblock David Wuertele
2010-07-08 9:11 ` Artem Bityutskiy [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=1278580312.12733.75.camel@localhost \
--to=dedekind1@gmail.com \
--cc=dave+gmane@wuertele.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;
as well as URLs for NNTP newsgroup(s).