From: hujianyang <hujianyang@huawei.com>
To: Daniel Ehrenberg <dehrenberg@google.com>
Cc: artem.bityutskiy@linux.intel.com,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Using UBIFS as an FTL
Date: Sat, 26 Jul 2014 07:41:57 +0800 [thread overview]
Message-ID: <53D2EB45.9060302@huawei.com> (raw)
In-Reply-To: <CAAK6Zt03J=0=tv5rPvZH0pTZWM8ha5eu0gqFbZ6P_FgSrgwW-A@mail.gmail.com>
On 2014/7/26 2:21, Daniel Ehrenberg wrote:
> - loopback-mounting a file on ubifs--From skimming the code, it looks
> to me like ubifs uses some nice datastructures to handle writes within
> a file without doing read-modify-writes all the time as ubiblock
> forces. ubifs authors/maintainers, do you see any downside to using
> ubifs this way?
This way seems most easily to realize. Synchronize the loop file and
maybe you will never worry about power cut.
How about using UBI-layer and writing a new block driver to handle
bio? This driver should care about which leb on the flash has data
and other thing else(I don't have a clear idea now). The 'leb_change'
ops in UBI-layer maybe helpful for in-place update and atomic write.
But This way is harder than using a loop file.
next prev parent reply other threads:[~2014-07-25 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 18:21 Using UBIFS as an FTL Daniel Ehrenberg
2014-07-25 23:41 ` hujianyang [this message]
2014-07-27 7:20 ` Richard Weinberger
2014-07-28 2:49 ` hujianyang
2014-07-28 3:06 ` Ezequiel Garcia
2014-07-28 6:56 ` Richard Weinberger
2014-07-28 16:54 ` Artem Bityutskiy
2014-07-28 17:47 ` Daniel Ehrenberg
2014-07-29 7:16 ` Artem Bityutskiy
2014-07-29 16:45 ` Daniel Ehrenberg
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=53D2EB45.9060302@huawei.com \
--to=hujianyang@huawei.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=dehrenberg@google.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