From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kartik Nagar <kartik.n.nagar@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Actual number of writes to a MTD device
Date: Tue, 26 Apr 2011 10:38:54 +0300 [thread overview]
Message-ID: <1303803534.2778.23.camel@localhost> (raw)
In-Reply-To: <loom.20110423T144945-306@post.gmane.org>
On Sat, 2011-04-23 at 12:55 +0000, Kartik Nagar wrote:
> Hi,
>
> I am using UBIFS on top of UBI on top of a MTD partition and then running some
> workloads on the UBIFS filesystem. I actually want to determine the write
> amplification factor for the workload, for which i need the actual number of
> writes going to the MTD device. Do UBIFS/MTD systems record such statistics, or
> will I have to make changes to the source code to obtain the statistics?
These statistics has to be done on MTD level, not in UBIFS. MTD does not
do this AFAIK.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-04-26 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 12:55 Actual number of writes to a MTD device Kartik Nagar
2011-04-25 10:47 ` Atlant Schmidt
2011-04-26 7:38 ` 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=1303803534.2778.23.camel@localhost \
--to=dedekind1@gmail.com \
--cc=kartik.n.nagar@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 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).