All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brijesh Singh <brijesh.s.singh@gmail.com>
Cc: linux-mtd@lists.infradead.org, rohitvdongre@gmail.com,
	David Woodhouse <dwmw2@infradead.org>,
	Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: Release of UBIL: ubi with log
Date: Mon, 10 May 2010 14:02:56 +0300	[thread overview]
Message-ID: <1273489376.2209.127.camel@localhost> (raw)
In-Reply-To: <h2h6b5362aa1005100203l7530e56eh1029efd4d1428b91@mail.gmail.com>

On Mon, 2010-05-10 at 14:33 +0530, Brijesh Singh wrote:
> Hi,
> 
> On Mon, May 10, 2010 at 12:19 PM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Fri, 2010-02-26 at 18:28 +0530, Brijesh Singh wrote:
> >> Hi,
> >>  It gives me great pleasure in sharing UBIL: ubi with log.  We have
> >> added logging functionality to ubi for reducing mount time.
> >> UBIL uses the "same source base of UBI". The logging functionality can
> >> be added or removed at compile time using "make menuconfig option".
> >>
> >> We have seen mount time reduction of 50% in 1GB NAND. We are expecting
> >> even better results for larger flash memories.
> >
> > Was that SLC or MLC NAND?
> 
> It was SLC NAND.
> 
> >> The source code of UBIL can be found in the following git tree:
> >> http://git.infradead.org/users/brijesh/ubi-2.6.git
> >>
> >> We have tested ubil for samsung nand and onenand. The test results can
> >> be found in the following git tree:
> >> http://git.infradead.org/users/brijesh/ubil_results
> >
> > Did you run any stress tests for UBIL? Which?
> 
> We ran
> 1) fsstress on UBIFS without power failure
> 2) fsstress on UBIFS with power failure

Please, run also the integck test which you can find in the mtd-utils,
it is a very good test, and I think it is better than fsstress even.

If integck will work, this will mean UBIL is quite stable. Then let's
make sure it does not regress when we introduce changes.

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

      parent reply	other threads:[~2010-05-10 11:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 12:58 Release of UBIL: ubi with log Brijesh Singh
2010-03-02 19:45 ` Artem Bityutskiy
2010-03-31 12:57   ` Corentin Chary
2010-03-31 12:59     ` Artem Bityutskiy
2010-04-01 18:54       ` Brijesh Singh
2010-04-01 11:14     ` Brijesh Singh
2010-04-01 11:59       ` Corentin Chary
2010-04-01 19:06         ` Brijesh Singh
2010-04-23 12:11           ` Artem Bityutskiy
2010-04-06  8:31 ` Artem Bityutskiy
2010-04-07  8:51   ` Brijesh Singh
2010-05-10  6:49 ` Artem Bityutskiy
2010-05-10  9:03   ` Brijesh Singh
2010-05-10  9:07     ` Artem Bityutskiy
2010-05-10 10:21       ` Brijesh Singh
2010-05-10 11:09         ` Artem Bityutskiy
2010-05-10 11:02     ` 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=1273489376.2209.127.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=adrian.hunter@nokia.com \
    --cc=brijesh.s.singh@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rohitvdongre@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 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.