From: Tanya Brokhman <tlinder@codeaurora.org>
To: Richard Weinberger <richard@nod.at>,
Artem Bityutskiy <dedekind1@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Dolev Raviv <draviv@codeaurora.org>
Subject: Synchronization in UBIFS (zero length files)
Date: Thu, 18 Dec 2014 10:34:23 +0200 [thread overview]
Message-ID: <5492918F.2060704@codeaurora.org> (raw)
Hi Artem/Richard
I've been looking into the "zero length files" issue in UBIFS and came
across "Synchronization exceptions for buggy applications" @
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_sync_semantics. This
section concludes with:
"We have plans to implement these features in UBIFS, but this has not
been done yet. The problem is that UBI/MTD are fully synchronous and we
cannot initiate asynchronous write-out, so we'd have to synchronously
write files on close/rename, which is slow. So implementing these
features would require implementing asynchronous I/O in UBI, which is a
big job. But feel free to do this :-)."
So two questions:
1. was anything done in ubifs to handle file truncation and rename
similar to ext4? Didn't find anything but afraid I might be missing
something
2. Not sure I understand why "implementing these features would require
implementing asynchronous I/O in UBI". Could you please elaborate on this?
Thanks,
Tanya Brokhman
--
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, a Linux Foundation Collaborative Project
next reply other threads:[~2014-12-18 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 8:34 Tanya Brokhman [this message]
2014-12-18 11:12 ` Synchronization in UBIFS (zero length files) Richard Weinberger
2014-12-18 14:53 ` Tanya Brokhman
2014-12-18 15:12 ` Richard Weinberger
2014-12-23 8:26 ` Tanya Brokhman
2014-12-23 9:24 ` Richard Weinberger
2014-12-23 9:48 ` Tanya Brokhman
2015-01-31 12:52 ` Artem Bityutskiy
2015-01-31 12:57 ` Bityutskiy, Artem
2015-02-01 8:39 ` Tanya Brokhman
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=5492918F.2060704@codeaurora.org \
--to=tlinder@codeaurora.org \
--cc=dedekind1@gmail.com \
--cc=draviv@codeaurora.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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.