All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Puschmann <andre.puschmann@stud.tu-ilmenau.de>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS on Atmel Dataflash
Date: Wed, 09 Dec 2009 10:55:51 +0100	[thread overview]
Message-ID: <4B1F7427.10002@stud.tu-ilmenau.de> (raw)
In-Reply-To: <1260348786.19669.1231.camel@localhost>

Hi Artem,

thanks for your prompt reply.

Artem Bityutskiy wrote:
> Yeah, I had a feeling we should not have assumed power of 2. But it was
> so appealing, because we can avoid (slow) divisions when aligning data
> to min. I/O unit boundary. I knew about DataFlash, but it is usually so
> small that I did not expect anyone using UBIFS there.
>
> Are you sure you want ubifs on such a tiny flash? We were really
> targeting to larger ones, say, starting from 64MiB at least.
>   
Mmh, the idea to run UBIFS came up due to a problem with JFFS2 on this
device. So I wanted to use another writeable flash fs to  find out
whether its a fs-problem or a mtd/dataflash one.

So you suggest to stick with JFFS2 in this case?

> Basically, there is not fundamental reasons not to support non-power of
> 2 min. I/O unit size, besides of optimizations. And to fix this, one
> would need to carefully look at / grep for min_io_size usage in both
> UBI/UBIFS, and change stuff like ALIGN(x, c->min_io_size) to something
> else. But there are very many of such places.
>   
Thanks for your explanation.


Best regards,

Andre

  reply	other threads:[~2009-12-09  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09  8:30 UBIFS on Atmel Dataflash Andre Puschmann
2009-12-09  8:53 ` Artem Bityutskiy
2009-12-09  9:55   ` Andre Puschmann [this message]
2009-12-09  9:57     ` Artem Bityutskiy
2009-12-09 14:33   ` 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=4B1F7427.10002@stud.tu-ilmenau.de \
    --to=andre.puschmann@stud.tu-ilmenau.de \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    /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.