Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nancy <nancydreaming@gmail.com>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI: question about ubi_leb_change
Date: Thu, 6 Mar 2008 22:14:51 +0800	[thread overview]
Message-ID: <bae050c10803060614x5a81a065ldbfacb33edf04b7@mail.gmail.com> (raw)
In-Reply-To: <1204811457.23706.49.camel@sauron>

> But UBI in now way can help you to solve this problem. How could it?
> Invent an interface which would help.
>
> The only way to go is to teach the FS which sits on top of you to inform
> you about all blocks which become free when something is deleted. But
> the existing FSes do not do this. An yes, this means you'll move garbage
> all over the place, which is slow.
>
> This is why we started UBIFS instead of doing FTL - because we assumed a
> native FS should be significantly more efficient then FTL.

But Windows do not recognize UBIFS.  I have to support VFAT to work on
UBI, how can I do? Guess I have nothing to do but suffer the slow
time. Now I just want to save a little time, do not
read the whole old mapped LEB back, but only necessary pages.  The
VFAT partitions usuallly use for storing  media data (mp3, mp4, avi
....). Only the filesystem meta-data stored area has much chance to be
little change.

So I needs some functions which I discribe before.  I met some problem
when I created them.
Maybe one more day will be fix,  or still can't, if it last too long
time still can't fix, hope I can get some help from you if you are
free.

Thank you :-)

---
Best wishes,
Nancy

      reply	other threads:[~2008-03-06 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 12:26 UBI: question about ubi_leb_change Nancy
2008-03-06 12:50 ` Artem Bityutskiy
2008-03-06 13:39   ` Nancy
2008-03-06 13:50     ` Artem Bityutskiy
2008-03-06 14:14       ` Nancy [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=bae050c10803060614x5a81a065ldbfacb33edf04b7@mail.gmail.com \
    --to=nancydreaming@gmail.com \
    --cc=dedekind@infradead.org \
    --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