From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: separate NOCoW and pinfile semantics
Date: Fri, 6 Sep 2019 10:47:34 +0800 [thread overview]
Message-ID: <5c583e7c-bb69-4bfb-9ff8-29182973c359@huawei.com> (raw)
In-Reply-To: <b5549a88-6805-99a8-4b0a-3bbf49da794c@huawei.com>
On 2019/8/6 9:36, Chao Yu wrote:
>>>> Now WAL mode were set by default in Android, so most of db file are -wal type now.
>>> Will be back again tho.
>> R?
> Q.
Jaegeuk, why we reuse persist mode in Q now?
Thanks,
prev parent reply other threads:[~2019-09-06 2:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 7:39 [PATCH v2] f2fs: separate NOCoW and pinfile semantics Chao Yu
2019-07-23 2:36 ` Jaegeuk Kim
2019-07-23 7:08 ` Chao Yu
2019-07-29 5:57 ` Jaegeuk Kim
2019-07-29 7:20 ` Chao Yu
2019-07-30 18:02 ` Jaegeuk Kim
2019-07-31 9:55 ` Chao Yu
2019-08-01 4:14 ` Jaegeuk Kim
2019-08-01 7:08 ` Chao Yu
2019-08-01 22:27 ` Jaegeuk Kim
2019-08-02 7:55 ` Chao Yu
2019-08-06 0:37 ` Jaegeuk Kim
2019-08-06 1:36 ` Chao Yu
2019-09-06 2:47 ` Chao Yu [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=5c583e7c-bb69-4bfb-9ff8-29182973c359@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).