From: Subodh Nijsure <snijsure@grid-net.com>
To: dedekind1@gmail.com
Cc: mtd <linux-mtd@lists.infradead.org>
Subject: Re: Comparing UBI volumes to generate patch for upgrades
Date: Fri, 03 Feb 2012 15:14:32 -0800 [thread overview]
Message-ID: <4F2C6A58.6060500@grid-net.com> (raw)
In-Reply-To: <1328260703.13362.3.camel@sauron.fi.intel.com>
On 02/03/2012 01:18 AM, Artem Bityutskiy wrote:
> On Wed, 2012-02-01 at 10:31 -0800, Subodh Nijsure wrote:
>> one option is use VCDIFF/bsdif or variation there-of and generate a
>> binary diff package.
>>
>> option 2 is write a tool that compares UBI volume layout for revision 1
>> and UBI volume layout for revision 2 and then send that difference,
>> along the lines of what is outlined in the paper @
>> http://www.icmu.org/icmu2010/Papers/3-1.pdf
> I guess you can do this for R/O volumes, but not R/W.
Yes we would do this 'upgrade' on read-only volume.
>
> Depending on how much extra flash you have, you may do the actual update
> in a power-off-tolerant manner or not.
Actually we do have to do this upgrade in power-off-tolerant manner, but
hardware does give us few seconds of "battery backed" power, and
indicates to software that shutdown is imminent.
>> We are just getting started writing a tool to compare UBI volumes, but I
>> want to send out querry to UBI experts to see if there are some
>> fundamental issues with UBI that would make comparing UBI volumes and
>> applying such a patch would be a non-starter.
> I assume you are not planning to do this stuff in kernel space, right?
Not planning to this in kernel space.
prev parent reply other threads:[~2012-02-03 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 18:31 Comparing UBI volumes to generate patch for upgrades Subodh Nijsure
2012-02-03 9:18 ` Artem Bityutskiy
2012-02-03 23:14 ` Subodh Nijsure [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=4F2C6A58.6060500@grid-net.com \
--to=snijsure@grid-net.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox