public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Shweta Shetty <shyamashweta@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Ubi2- using NandSim for simulating flash and mounting ubi.
Date: Sat, 16 Jan 2010 23:14:40 +0200	[thread overview]
Message-ID: <1263676480.8276.107.camel@localhost.localdomain> (raw)
In-Reply-To: <c58fcbf21001080316j4ff51fe6wcb20eefd0d57e101@mail.gmail.com>

Hi,

sorry, I am not sure understand the question.

On Fri, 2010-01-08 at 16:46 +0530, Shweta Shetty wrote:
> Hi,
> 
> To test ubi2 we intend to use NANDSIM. However we are facing certain problems.
> 
> From what we have understood, the method of using NANDSIM is :
> 1>create an empty flash device (By default this uses the ram memory
> but we can allocate other by the cache_file option)
> 2>mount ubi on it
> 3>mount ubifs on it
> => (Here we can load the previously stored image)

If you want to write some pre-created image (e.g., created with
mkfs.ubifs/ubinize) or previously saved image (e.g., you dumped
your /dev/mtdX to a file previously), then you have to do this _before_
attaching the MTD device to UBI. IOW, you have to do this between steps
1 and 2.

> 4>use it
> 5>while unmounting save the image on permanant storage

After you have unmounted everything, you can save it, yes.

> So as we can see, though NANDSIM can be effectively used for
> simulating flash , it is of limited use in our project for testing
> mount time as every time only the empty device is mounted.

No. You can write your contents there before mounting.

> From the ubi code that we have now studied , there is a flag set for
> an empty device and in such case , all the system does is that it
> initialises all its data structures.

It does this _only_ if you feed it an empty flash. Do not feed it an
empty flash, feed it a formatted flash, then it will not initialize it.

> Hence we cannot show the
> performance of our project on NANDSIM.

Well, of course in any case, performance is better shown on a real
device.

> Our we missing some crucial point?
> We would be grateful for clarification.

Not sure I clarified, because I did not really understand the question,
but HTH.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2010-01-16 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08 11:16 Ubi2- using NandSim for simulating flash and mounting ubi Shweta Shetty
2010-01-16 21:14 ` Artem Bityutskiy [this message]
2010-01-21 12:25   ` Shweta Shetty

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=1263676480.8276.107.camel@localhost.localdomain \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shyamashweta@gmail.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