From: "赵南哲 via Linux-f2fs-devel" <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: "Barry Song" <baohua@kernel.org>,
"Juan Yescas" <jyescas@google.com>, "Dev Jain" <Dev.Jain@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"David Hildenbrand" <David.Hildenbrand@arm.com>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
张博 <zhangbo56@xiaomi.com>,
"Kalesh Singh" <kaleshsingh@google.com>,
"Nanzhe Zhao" <nzzhao@126.com>, 李鹏飞 <lipengfei28@xiaomi.com>,
"Ryan Roberts" <Ryan.Roberts@arm.com>
Subject: [f2fs-dev] 答复: [External Mail]Re: [PATCH v2 00/14] f2fs: support & optimize large folios for writable files
Date: Sat, 3 Oct 2026 13:40:16 +0000 [thread overview]
Message-ID: <6ccdf4eef9b242bc96d28d511f754a30@xiaomi.com> (raw)
In-Reply-To: <ar1CJBRumJ0hcNdB@google.com>
Hi Jaeguk:
Oh......, I'm on holiday from Oct 1 to Oct 7,so the next version may not be
that soon and I apologize fot that. I'will catch on that once I've got time.
Thanks,
Nanzhe
#/******本邮件及其附件含有小米公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from XIAOMI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!******/#
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-10-03 13:56 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 4:18 [f2fs-dev] [PATCH v2 00/14] f2fs: support & optimize large folios for writable files Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:18 ` [f2fs-dev] [PATCH v2 01/14] f2fs: extend folio state for large folio write path Nanzhe Zhao via Linux-f2fs-devel
2026-09-16 9:53 ` Chao Yu via Linux-f2fs-devel
2026-09-15 4:18 ` [f2fs-dev] [PATCH v2 02/14] f2fs: carry subpage offset and count in write IO Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:18 ` [f2fs-dev] [PATCH v2 03/14] f2fs: support regular file buffered writes on large folios Nanzhe Zhao via Linux-f2fs-devel
2026-09-16 11:47 ` Chao Yu via Linux-f2fs-devel
2026-09-29 17:41 ` Daeho Jeong
2026-10-08 5:33 ` Nanzhe Zhao via Linux-f2fs-devel
2026-10-02 17:02 ` Daeho Jeong
2026-10-08 5:46 ` Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:18 ` [f2fs-dev] [PATCH v2 04/14] f2fs: support atomic file large folios buffered write Nanzhe Zhao via Linux-f2fs-devel
2026-09-16 12:07 ` Chao Yu via Linux-f2fs-devel
2026-09-23 3:21 ` Nanzhe Zhao via Linux-f2fs-devel
2026-09-23 7:22 ` Chao Yu via Linux-f2fs-devel
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 05/14] f2fs: support large folio writeback Nanzhe Zhao via Linux-f2fs-devel
2026-09-17 3:48 ` Chao Yu via Linux-f2fs-devel
2026-09-21 2:52 ` Chao Yu via Linux-f2fs-devel
2026-10-02 20:51 ` Daeho Jeong
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 06/14] f2fs: prepare mmap write faults for large folios Nanzhe Zhao via Linux-f2fs-devel
2026-09-17 6:32 ` Chao Yu via Linux-f2fs-devel
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 07/14] f2fs: make GC migration large-folio aware Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 08/14] f2fs: optimize small block size large folio read Nanzhe Zhao via Linux-f2fs-devel
2026-09-16 4:33 ` Daeho Jeong
2026-09-23 2:36 ` Nanzhe Zhao via Linux-f2fs-devel
2026-09-24 1:34 ` Nanzhe Zhao via Linux-f2fs-devel
2026-09-17 8:09 ` Chao Yu via Linux-f2fs-devel
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 09/14] f2fs: support partial uptodate " Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 10/14] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao via Linux-f2fs-devel
2026-09-17 8:30 ` Chao Yu via Linux-f2fs-devel
2026-09-23 2:50 ` Nanzhe Zhao via Linux-f2fs-devel
2026-09-23 7:18 ` Chao Yu via Linux-f2fs-devel
2026-09-17 8:32 ` Chao Yu via Linux-f2fs-devel
2026-09-15 4:25 ` [f2fs-dev] [PATCH v2 11/14] f2fs: fix zeroing paths for large folios Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:25 ` [f2fs-dev] [PATCH v2 12/14] f2fs: handle block cloning within the same large folio Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:25 ` [f2fs-dev] [PATCH v2 13/14] f2fs: allow large folio support to writeable files Nanzhe Zhao via Linux-f2fs-devel
2026-09-17 14:07 ` Chao Yu via Linux-f2fs-devel
2026-09-15 4:25 ` [f2fs-dev] [PATCH v2 14/14] f2fs: make compressed files compatible with large folio Nanzhe Zhao via Linux-f2fs-devel
2026-09-22 3:09 ` Chao Yu via Linux-f2fs-devel
2026-09-30 17:08 ` [f2fs-dev] [PATCH v2 00/14] f2fs: support & optimize large folios for writable files Jaegeuk Kim via Linux-f2fs-devel
2026-10-03 13:40 ` 赵南哲 via Linux-f2fs-devel [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=6ccdf4eef9b242bc96d28d511f754a30@xiaomi.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=David.Hildenbrand@arm.com \
--cc=Dev.Jain@arm.com \
--cc=Ryan.Roberts@arm.com \
--cc=baohua@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jyescas@google.com \
--cc=kaleshsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lipengfei28@xiaomi.com \
--cc=nzzhao@126.com \
--cc=zhangbo56@xiaomi.com \
--cc=zhaonanzhe@xiaomi.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 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.