public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Willy Tarreau <w@1wt.eu>
Cc: piergiorgio.beruto@gmail.com, Mike Frysinger <vapier@gentoo.org>,
	linux-mtd@lists.infradead.org,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: Ubiblock users call (Re: mvneta / openblocks switch)
Date: Wed, 6 Nov 2013 07:59:52 -0300	[thread overview]
Message-ID: <20131106105951.GA2616@localhost> (raw)
In-Reply-To: <20131106063007.GA17145@1wt.eu>

On Wed, Nov 06, 2013 at 07:30:07AM +0100, Willy Tarreau wrote:
> Hi Ezequiel,
> 
> On Tue, Nov 05, 2013 at 03:57:48PM +0100, Willy Tarreau wrote:
> > > Can you describe your usage?
> >
> > For example, one of my distro's boot scripts automatically detects
> > the available partitions, checks for a mountable FS there, then
> > locates the current config and loads it. With a block device, I have
> > nothing to change at all. With other solutions, I have to reconsider
> > the boot process.
> 
> BTW, I forgot to describe the initial use case I had in mind which led to this:
> many of my machines (including the test ones) boot from a rootfs which is a
> squashfs stored as an initrd image. At the moment, the squashfs is read by
> u-boot from the NAND into memory and the kernel boots from this. Loading a 10
> MB rootfs from NAND to RAM takes 1-2 seconds depending on the device, and
> consumes 10 MB of RAM all the time. Also, you're always at risk that some bad
> blocks appear in the middle of this image (I had one device where I had to
> change the location of the initrd partition because of
> this).
> 
> With ubiblock, I can totally solve this issue :
>   - u-boot does not read anymore the initrd, thus saving time and RAM
>   - kernel simply mounts the squashfs at boot from ubiblock, resulting
>     in direct accesses
>   - ubi would take care of bad blocks itself
> 
> Doing so prevents me from upgrading the image since it's always mounted,
> which is why I wanted to try to write it from u-boot. It did not work so
> I wanted to use 2 images and upgrade one while running on the other one.
> But I did not make any progress on this yet.
> 
> I'll definitely give your latest patches a try, I just don't know when :-)
> 

Thanks for all these details! It'll be definitely interesting if you
could jump in the discussion when the patch is finally submitted.
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

      reply	other threads:[~2013-11-06 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131031135322.GN26784@titan.lakedaemon.net>
     [not found] ` <52738D6A.1010900@hitachi.com>
     [not found]   ` <20131101130528.716e53d9@skate>
     [not found]     ` <20131105103555.GD16420@1wt.eu>
     [not found]       ` <5278E824.8050405@hitachi.com>
     [not found]         ` <20131105135323.GA17316@1wt.eu>
2013-11-05 14:40           ` Ubiblock users call (Re: mvneta / openblocks switch) Ezequiel Garcia
2013-11-05 14:57             ` Willy Tarreau
2013-11-06  6:30               ` Willy Tarreau
2013-11-06 10:59                 ` Ezequiel Garcia [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=20131106105951.GA2616@localhost \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=piergiorgio.beruto@gmail.com \
    --cc=vapier@gentoo.org \
    --cc=w@1wt.eu \
    /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