From: Gao Xiang <hsiangkao@linux.alibaba.com> To: linux-erofs@lists.ozlabs.org Cc: linux-fsdevel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>, nvdimm@lists.linux.dev, "Darrick J. Wong" <djwong@kernel.org>, Liu Bo <bo.liu@linux.alibaba.com>, Joseph Qi <joseph.qi@linux.alibaba.com>, Liu Jiang <gerry@linux.alibaba.com>, Gao Xiang <hsiangkao@linux.alibaba.com> Subject: [RFC PATCH 0/2] erofs: dio/dax support for non-tailpacking cases Date: Sun, 4 Jul 2021 21:50:54 +0800 [thread overview] Message-ID: <20210704135056.42723-1-hsiangkao@linux.alibaba.com> (raw) Hi folks, This patchset mainly adds preliminary EROFS iomap dio/dax support for non-tailpacking uncompressed cases. Direct I/O is useful in certain scenarios for uncompressed files. For example, double pagecache can be avoid by direct I/O when loop device is used for uncompressed files containing upper layer compressed filesystem. Also, DAX is quite useful for some VM use cases in order to save guest memory extremely by using the minimal lightweight EROFS. Tail-packing inline iomap support will be handled later since currently iomap doesn't support such data pattern, which is independent to non-tailpacking cases. Comments are welcome. Thanks for your time on reading this! Thanks, Gao Xiang Gao Xiang (1): erofs: dax support for non-tailpacking regular file Huang Jianan (1): erofs: iomap support for non-tailpacking DIO fs/erofs/Kconfig | 1 + fs/erofs/data.c | 143 +++++++++++++++++++++++++++++++++++++++++++- fs/erofs/inode.c | 10 +++- fs/erofs/internal.h | 3 + fs/erofs/super.c | 20 ++++++- 5 files changed, 173 insertions(+), 4 deletions(-) -- 2.24.4
WARNING: multiple messages have this Message-ID (diff)
From: Gao Xiang <hsiangkao@linux.alibaba.com> To: linux-erofs@lists.ozlabs.org Cc: nvdimm@lists.linux.dev, "Darrick J. Wong" <djwong@kernel.org>, LKML <linux-kernel@vger.kernel.org>, Joseph Qi <joseph.qi@linux.alibaba.com>, Liu Bo <bo.liu@linux.alibaba.com>, linux-fsdevel@vger.kernel.org, Gao Xiang <hsiangkao@linux.alibaba.com>, Liu Jiang <gerry@linux.alibaba.com> Subject: [RFC PATCH 0/2] erofs: dio/dax support for non-tailpacking cases Date: Sun, 4 Jul 2021 21:50:54 +0800 [thread overview] Message-ID: <20210704135056.42723-1-hsiangkao@linux.alibaba.com> (raw) Hi folks, This patchset mainly adds preliminary EROFS iomap dio/dax support for non-tailpacking uncompressed cases. Direct I/O is useful in certain scenarios for uncompressed files. For example, double pagecache can be avoid by direct I/O when loop device is used for uncompressed files containing upper layer compressed filesystem. Also, DAX is quite useful for some VM use cases in order to save guest memory extremely by using the minimal lightweight EROFS. Tail-packing inline iomap support will be handled later since currently iomap doesn't support such data pattern, which is independent to non-tailpacking cases. Comments are welcome. Thanks for your time on reading this! Thanks, Gao Xiang Gao Xiang (1): erofs: dax support for non-tailpacking regular file Huang Jianan (1): erofs: iomap support for non-tailpacking DIO fs/erofs/Kconfig | 1 + fs/erofs/data.c | 143 +++++++++++++++++++++++++++++++++++++++++++- fs/erofs/inode.c | 10 +++- fs/erofs/internal.h | 3 + fs/erofs/super.c | 20 ++++++- 5 files changed, 173 insertions(+), 4 deletions(-) -- 2.24.4
next reply other threads:[~2021-07-04 13:51 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-04 13:50 Gao Xiang [this message] 2021-07-04 13:50 ` [RFC PATCH 0/2] erofs: dio/dax support for non-tailpacking cases Gao Xiang 2021-07-04 13:50 ` [RFC PATCH 1/2] erofs: iomap support for non-tailpacking DIO Gao Xiang 2021-07-04 13:50 ` Gao Xiang 2021-07-04 13:50 ` [RFC PATCH 2/2] erofs: dax support for non-tailpacking regular file Gao Xiang 2021-07-04 13:50 ` Gao Xiang 2021-07-04 16:00 ` kernel test robot 2021-07-05 13:21 ` [RFC PATCH v1.1 " Gao Xiang 2021-07-05 13:21 ` Gao Xiang 2021-07-09 1:47 ` Darrick J. Wong 2021-07-09 1:47 ` Darrick J. Wong 2021-07-09 2:28 ` Gao Xiang 2021-07-09 2:28 ` Gao Xiang
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=20210704135056.42723-1-hsiangkao@linux.alibaba.com \ --to=hsiangkao@linux.alibaba.com \ --cc=bo.liu@linux.alibaba.com \ --cc=djwong@kernel.org \ --cc=gerry@linux.alibaba.com \ --cc=joseph.qi@linux.alibaba.com \ --cc=linux-erofs@lists.ozlabs.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=nvdimm@lists.linux.dev \ /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: linkBe 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.