public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Brijesh Singh <brij.singh@samsung.com>,
	"brijesh.s.singh@gmail.com" <brijesh.s.singh@gmail.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"rohitvdongre@gmail.com" <rohitvdongre@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	"Hunter Adrian \(Nokia-D/Helsinki\)" <adrian.hunter@nokia.com>
Subject: Re: Release of UBIL: ubi with log
Date: Wed, 31 Mar 2010 15:59:08 +0300	[thread overview]
Message-ID: <1270040348.15073.8.camel@localhost> (raw)
In-Reply-To: <t2q71cd59b01003310557v3c2b0775o6e90af812067e726@mail.gmail.com>

On Wed, 2010-03-31 at 14:57 +0200, ext Corentin Chary wrote:
> On Tue, Mar 2, 2010 at 8:45 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.
> >>
> >> The source code of UBIL can be found in the following git tree:
> >> http://git.infradead.org/users/brijesh/ubi-2.6.git
> >>
> >
> > Sounds interesting! However, I'm out of office till end of March, and
> > won't be able to look closely at this. But hopefully others will try it.
> >
> 
> Hi,
> Didn't took the time  to read the code, I'll try to do so soon.
> Could you tell us more about what you did and how it works ?
> Is it similar to yaffs checkpoints ? When are the log written ?
> What will happen if you try to mount something that used UBIL with a
> kernel without UBIL support ?
> Thanks,

Right. 

And Brijesh, just go ahead, split your stuff on patches, and submit them
to the MTD ML. Send your docs/URL to docs there as well.

Please, do not wait, just go ahead and start pushing it out.

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

  reply	other threads:[~2010-03-31 12:59 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 [this message]
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

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=1270040348.15073.8.camel@localhost \
    --to=artem.bityutskiy@nokia.com \
    --cc=adrian.hunter@nokia.com \
    --cc=brij.singh@samsung.com \
    --cc=brijesh.s.singh@gmail.com \
    --cc=corentin.chary@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox