From: Richard Weinberger <richard@nod.at>
To: 辉少 <wang502742203@qq.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: 回复： UBIFS: FileSystem Background Thread
Date: Fri, 1 Jul 2016 17:03:12 +0200 [thread overview]
Message-ID: <57768630.4020308@nod.at> (raw)
In-Reply-To: <tencent_0A4CA0E45DBD0DC1086D0099@qq.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 416 bytes --]
Am 01.07.2016 um 16:55 schrieb »ÔÉÙ:
> 1. You mean in async mode file is written to flash by writeback mechanism? If so, background thread has nothing to do with writing file to flash?
I'd not say nothing, it does the commit.
> 2. In sync mode, is writting finished by ubifs background thread or calling thread calling write()?
The calling thread.
Please start reading the UBIFS source code.
Thanks,
//richard
prev parent reply other threads:[~2016-07-01 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 13:50 UBIFS: FileSystem Background Thread =?gb18030?B?u9TJ2Q==?=
2016-07-01 14:13 ` Richard Weinberger
[not found] ` <tencent_0A4CA0E45DBD0DC1086D0099@qq.com>
2016-07-01 15:03 ` Richard Weinberger [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=57768630.4020308@nod.at \
--to=richard@nod.at \
--cc=linux-mtd@lists.infradead.org \
--cc=wang502742203@qq.com \
/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;
as well as URLs for NNTP newsgroup(s).