linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brijesh Singh <brijesh.s.singh@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-mtd@lists.infradead.org, rohitvdongre@gmail.com
Subject: Re: UBIL design doc
Date: Wed, 12 May 2010 13:01:21 +0300	[thread overview]
Message-ID: <1273658481.22706.73.camel@localhost> (raw)
In-Reply-To: <AANLkTikRDNia3IMCbXFs-olREPftszw-zqn3ruXCk-QE@mail.gmail.com>

On Wed, 2010-05-12 at 15:19 +0530, Brijesh Singh wrote:
> >> Any thing goes bad, normal scanning becomes recovery.
> >> 5) Not sure if log is required in first place. But it could be an option.
> >> Is that correct?
> >
> > No, at least I did not suggest you to get rid of the log. It is needed
> > to handle unclean reboots.
> Log is written for each EC or VID change.

Yes, I understand.

>  Frequency of log write is same as
> the frequency of these headers.

Right.

>  In case we keep both, there will be one log
> write penalty per write/erase.

Yes, each time you write to an unmapped LEB, you write the VID header
and a log entry.

>  So write performance will drop considerably.

Not sure about 'considerably'. This is to be tested. Keeping the headers
means 1 additional write per peb_size bytes, right? Plus just after
erase, EC header should be written. But this is the price you pay for
robustness and compatibility.

But again, it is very easy to switch off headers if this is needed,
isn't it?

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

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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-08 19:39 UBIL design doc Brijesh Singh
2010-05-10  7:15 ` Artem Bityutskiy
2010-05-10 10:31   ` Brijesh Singh
2010-05-11 19:17   ` Thomas Gleixner
2010-05-12  7:03     ` Brijesh Singh
2010-05-12  7:14       ` Brijesh Singh
2010-05-12  9:02       ` Thomas Gleixner
2010-05-12  9:46         ` Brijesh Singh
2010-05-12  7:41     ` Artem Bityutskiy
2010-05-12  8:03       ` Brijesh Singh
2010-05-12  8:35         ` Artem Bityutskiy
2010-05-12  9:49           ` Brijesh Singh
2010-05-12 10:01             ` Artem Bityutskiy [this message]
2010-05-12 10:25               ` Brijesh Singh
2010-05-12 10:58             ` Thomas Gleixner
2010-05-13  7:10               ` Brijesh Singh
2010-05-12  9:06       ` Thomas Gleixner
2010-05-12  9:31         ` 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=1273658481.22706.73.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=brijesh.s.singh@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rohitvdongre@gmail.com \
    --cc=tglx@linutronix.de \
    /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).