From: Robert Homann <homann@bury.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Resizing of an existing UBIFS
Date: Tue, 22 May 2012 13:11:57 +0200 [thread overview]
Message-ID: <4FBB747D.10804@bury.com> (raw)
In-Reply-To: <1337681963.2483.140.camel@sauron.fi.intel.com>
On 05/22/2012 12:19 PM, Artem Bityutskiy wrote:
> Yeah, if someone wrote such a tool, it would make sense to support
> shrinking as well, because it is roughly a similar thin - you need to
> relocate data from the end, amend the index and probably some other
> UBIFS data-structures.
This is getting interesting.
On which level would such a tool operate? I guess it would have to do some
low-level operations directly on UBIFS structures, but it would use the UBI
layer below only to get at the corresponding blocks. Other than that, the UBI
structures would not require direct manipulations, am I right? In this case,
such a tool could be implemented without strict dependency on UBI.
Or would it be necessary to also touch UBI structures directly, in which case
I guess it would become much more messy?
Best regards,
Robert Homann
next prev parent reply other threads:[~2012-05-22 11:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 6:41 Resizing of an existing UBIFS Robert Homann
2012-05-22 6:53 ` Artem Bityutskiy
2012-05-22 7:21 ` Robert Homann
2012-05-22 8:10 ` Artem Bityutskiy
2012-05-22 9:25 ` Robert Homann
2012-05-22 9:40 ` Ricard Wanderlof
2012-05-22 10:19 ` Artem Bityutskiy
2012-05-22 11:11 ` Robert Homann [this message]
2012-05-22 11:24 ` Artem Bityutskiy
2012-05-25 7:00 ` Adrian Hunter
2012-05-25 7:49 ` Robert Homann
2012-05-25 8:00 ` Ricard Wanderlof
2012-05-28 9:09 ` Adrian Hunter
2012-06-01 10:10 ` Ricard Wanderlof
2012-06-01 11:48 ` Adrian Hunter
2012-06-01 19:47 ` Ricard Wanderlof
2012-06-04 7:58 ` Adrian Hunter
2012-06-04 9:35 ` Ricard Wanderlof
2012-06-04 9:47 ` Artem Bityutskiy
2012-05-25 10:12 ` Norbert van Bolhuis
2012-05-26 14:00 ` Artem Bityutskiy
2012-05-27 20:24 ` Norbert van Bolhuis
2012-05-28 5:46 ` 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=4FBB747D.10804@bury.com \
--to=homann@bury.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 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.