All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mkfs.jffs2 min erase block size: 4 vs 8 KiB
Date: Fri, 24 Jun 2011 22:29:34 +0300	[thread overview]
Message-ID: <1308943791.13493.16.camel@koala> (raw)
In-Reply-To: <BANLkTimkgCz_yBnDOXyafhSV5S+R1un_YQ@mail.gmail.com>

On Fri, 2011-06-24 at 15:23 -0400, Mike Frysinger wrote:
> > Yes, the other way is to teach JFFS2 to merge PEBs and work with
> > multiple of PEBs. In fact in the past it could do this, but that was
> > removed because of some issues, do not remember what.
> >
> > The only complication I see is bad blocks. When you merge PEBs and one
> > of them is bad, then the good PEBs which are in this merge should be
> > treated as bad as well. But this should not be very difficult to do.
> >
> > On the one hand, teaching JFFS2 deal with small PEBs seems to make more
> > sense, on the other hand, doing this on driver level has an advantage -
> > you do not have to modify the file-system and you automatically make UBI
> > benefit from this - UBI scan time goes down when eraseblocks become
> > larger.
> 
> this is way above my familiarity with the code base.  i'll just post
> patches to update the docs.

Fair enough - ones who really need to solve this issue can work on it -
no need to do that if you do not really need this now.

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

      reply	other threads:[~2011-06-24 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22  5:02 mkfs.jffs2 min erase block size: 4 vs 8 KiB Mike Frysinger
2011-06-22  8:30 ` Guillaume LECERF
2011-06-24 12:07 ` Artem Bityutskiy
2011-06-24 17:10   ` Mike Frysinger
2011-06-24 19:20     ` Artem Bityutskiy
2011-06-24 19:23       ` Mike Frysinger
2011-06-24 19:29         ` 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=1308943791.13493.16.camel@koala \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vapier.adi@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.