public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "Artem B. Bityutskiy" <dedekind@infradead.org>
Cc: zhao forrest <zhao_fusheng@hotmail.com>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH]Add JFFS2 eraseblock header support
Date: Tue, 20 Sep 2005 14:27:47 +0200	[thread overview]
Message-ID: <20050920122747.GA4634@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1127217365.20014.45.camel@sauron.oktetlabs.ru>

On Tue, 20 September 2005 15:56:04 +0400, Artem B. Bityutskiy wrote:
> On Tue, 2005-09-20 at 13:36 +0200, Jörn Engel wrote:
> > > 
> > > If old binary mounts new image, it starts writing its cleanmarkers, use
> > > 1:N mapping etc. A "mixed" image appears. Afterwords, if this mixed
> > > image is being mounted on new JFFS2 binary, what poor Zhao is supposed
> > > to do? There will be too much ugliness in the code to handle that.
> > 
> > Please don't mix those two problems.  1:1 mapping has been dealt with.
> > If you don't like how it has been dealt with, complain in the context
> > of 1:1 mapping.
> 
> Please, remember the original goal. It is new wear-levelling. This patch
> may be considered as something independent, but it is not optimal. If we
> follow this way, Zhao must:
> 
> 1. Write code which understands both cleanmarkers and EB headers.
> 2. Test that old images are actually work well on new JFFS2.
> 3. Implement 1:1. Remove cleanmarkers support as they are not needed
> anymore.

Not quite.  He must:
1. Assume 1:1 mapping.  If people are not, that's a completely
   seperate problem.
2. Write robust code that does not depend on EBH.  If the header is
   missing, it should just create a new one and initialize its members
   as best it can - e.g. taking the average erase count.
3. Not emit clean markers anymore - they are not needed.

Going back to your list:

> 1. Write code which understands both cleanmarkers and EB headers.

Big deal.  Cleanmarker doesn't really matter, absence of EBH does.

> 2. Test that old images are actually work well on new JFFS2.

Sure!

> 3. Implement 1:1. Remove cleanmarkers support as they are not needed
> anymore.

Nope, why do you keep bringing it up?  1:1 is finished.  History.
Dealt with.  Old coffee.  Not a problem anymore.  Capisci?

Jörn

-- 
You ain't got no problem, Jules. I'm on the motherfucker. Go back in
there, chill them niggers out and wait for the Wolf, who should be
coming directly.
-- Marsellus Wallace

  reply	other threads:[~2005-09-20 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-20  7:45 [PATCH]Add JFFS2 eraseblock header support zhao forrest
2005-09-20 10:24 ` Jörn Engel
2005-09-20 10:59   ` Artem B. Bityutskiy
2005-09-20 11:36     ` Jörn Engel
2005-09-20 11:56       ` Artem B. Bityutskiy
2005-09-20 12:27         ` Jörn Engel [this message]
2005-09-20 12:43           ` Jörn Engel
2005-09-21  2:57       ` zhao forrest
2005-09-21  7:10         ` Jörn Engel
2005-09-21 10:42           ` Ferenc Havasi
2005-09-21  2:16     ` zhao forrest
2005-09-20 11:29 ` Artem B. Bityutskiy
2005-09-21  2:22   ` zhao forrest

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=20050920122747.GA4634@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=zhao_fusheng@hotmail.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