From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Raiger Helmut <helmut.raiger@hale.at>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS: How to reserve space to be used right before power cut
Date: Thu, 13 Jun 2013 16:20:28 +0200 [thread overview]
Message-ID: <20130613162028.3d17bac2@parrot.com> (raw)
In-Reply-To: <1142745477.330790.1371130164128.JavaMail.root@mail.hale>
Le Thu, 13 Jun 2013 14:29:24 +0100,
Raiger Helmut <helmut.raiger@hale.at> a écrit :
>
>
> > ----- Original Message -----
> > From: "Matthieu CASTET" <matthieu.castet@parrot.com>
> > To: "Helmut Raiger" <helmut.raiger@hale.at>
> > Cc: linux-mtd@lists.infradead.org
> > Sent: Thursday, June 13, 2013 1:50:31 PM
> > Subject: Re: UBIFS: How to reserve space to be used right before
> > power cut
> >
> > Hi,
> >
> > Why do you do this in ubifs ?
> >
> > If you do it in ubi/mtd this will be a lot's of easier.
> >
> > Matthieu
>
> I wasn't aware of an userspace interface for ubi/mtd, but just found
> out about gluebi. Is this the path you suggest?
>
> Could you please elaborate a bit more on this, I'm still unsure if
> this will meet our timing constraints (background operation of ubi?)
>
Not gluebi
you have a userspace inferface to ubi : /usr/include/mtd/ubi-user.h
You could create a small ubi volume (dynamic or static) of 1 LEB next to
ubifs (on the same ubi device).
When you start you make sure the LEB have enough space and that the LEB
is mapped.
on a power fail signal you write the LEB with your data. Because the
LEB is already mapped, the write should be imediate.
If the ubi volume is on the same ubi device than ubifs, the wear
leveling will be shared with ubifs.
next prev parent reply other threads:[~2013-06-13 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 11:42 UBIFS: How to reserve space to be used right before power cut Helmut Raiger
2013-06-13 11:50 ` Matthieu CASTET
2013-06-13 13:29 ` Raiger Helmut
2013-06-13 14:20 ` Matthieu CASTET [this message]
2013-06-17 9:02 ` Helmut Raiger
2013-06-26 8:03 ` Helmut Raiger
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=20130613162028.3d17bac2@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=helmut.raiger@hale.at \
--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.