From: Gao Xiang <hsiangkao@linux.alibaba.com> To: linux-erofs@lists.ozlabs.org, linux-fsdevel@vger.kernel.org Cc: LKML <linux-kernel@vger.kernel.org>, "Darrick J. Wong" <djwong@kernel.org>, Christoph Hellwig <hch@infradead.org>, Chao Yu <chao@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: [PATCH 0/2] erofs: iomap support for tailpacking cases Date: Fri, 16 Jul 2021 13:07:22 +0800 [thread overview] Message-ID: <20210716050724.225041-1-hsiangkao@linux.alibaba.com> (raw) Hi folks, non-tailpacking I/O: https://lore.kernel.org/r/20210712120241.199903-1-hsiangkao@linux.alibaba.com This patchset is a follow-up patchset of the previous patchset and interacts with iomap itself, whcih mainly adds preliminary EROFS iomap support for all tackpacking inline cases and has been preliminary tested myself. It only covers iomap read path. The write path remains untouched and bail out with -EIO if inline data with pos != 0 since EROFS cannot be used for actual testing. It'd be better to be implemented if upcoming fs users care rather than leave untested dead code around in kernel. Hopefully [PATCH 1/2] could be landed in iomap for-next independently since it has few changes / iomap-specific and the rest patches can be rebased upon iomap for-next then. Comments are welcome. Thanks for your time on reading this! Thanks, Gao Xiang Gao Xiang (2): iomap: support tail packing inline read erofs: convert all uncompressed cases to iomap fs/erofs/data.c | 288 +++++++---------------------------------- fs/iomap/buffered-io.c | 41 +++++- fs/iomap/direct-io.c | 8 +- 3 files changed, 90 insertions(+), 247 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, linux-fsdevel@vger.kernel.org Cc: "Darrick J. Wong" <djwong@kernel.org>, LKML <linux-kernel@vger.kernel.org>, Christoph Hellwig <hch@infradead.org>, Joseph Qi <joseph.qi@linux.alibaba.com>, Liu Bo <bo.liu@linux.alibaba.com>, Gao Xiang <hsiangkao@linux.alibaba.com>, Liu Jiang <gerry@linux.alibaba.com> Subject: [PATCH 0/2] erofs: iomap support for tailpacking cases Date: Fri, 16 Jul 2021 13:07:22 +0800 [thread overview] Message-ID: <20210716050724.225041-1-hsiangkao@linux.alibaba.com> (raw) Hi folks, non-tailpacking I/O: https://lore.kernel.org/r/20210712120241.199903-1-hsiangkao@linux.alibaba.com This patchset is a follow-up patchset of the previous patchset and interacts with iomap itself, whcih mainly adds preliminary EROFS iomap support for all tackpacking inline cases and has been preliminary tested myself. It only covers iomap read path. The write path remains untouched and bail out with -EIO if inline data with pos != 0 since EROFS cannot be used for actual testing. It'd be better to be implemented if upcoming fs users care rather than leave untested dead code around in kernel. Hopefully [PATCH 1/2] could be landed in iomap for-next independently since it has few changes / iomap-specific and the rest patches can be rebased upon iomap for-next then. Comments are welcome. Thanks for your time on reading this! Thanks, Gao Xiang Gao Xiang (2): iomap: support tail packing inline read erofs: convert all uncompressed cases to iomap fs/erofs/data.c | 288 +++++++---------------------------------- fs/iomap/buffered-io.c | 41 +++++- fs/iomap/direct-io.c | 8 +- 3 files changed, 90 insertions(+), 247 deletions(-) -- 2.24.4
next reply other threads:[~2021-07-16 5:07 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-16 5:07 Gao Xiang [this message] 2021-07-16 5:07 ` [PATCH 0/2] erofs: iomap support for tailpacking cases Gao Xiang 2021-07-16 5:07 ` [PATCH 1/2] iomap: support tail packing inline read Gao Xiang 2021-07-16 5:07 ` Gao Xiang 2021-07-16 9:19 ` Christoph Hellwig 2021-07-16 9:19 ` Christoph Hellwig 2021-07-16 9:46 ` Gao Xiang 2021-07-16 9:46 ` Gao Xiang 2021-07-16 13:47 ` Matthew Wilcox 2021-07-16 13:47 ` Matthew Wilcox 2021-07-16 14:38 ` Matthew Wilcox 2021-07-16 14:38 ` Matthew Wilcox 2021-07-16 13:02 ` Matthew Wilcox 2021-07-16 13:02 ` Matthew Wilcox 2021-07-16 13:56 ` Gao Xiang 2021-07-16 13:56 ` Gao Xiang 2021-07-16 14:44 ` Matthew Wilcox 2021-07-16 15:03 ` Gao Xiang 2021-07-16 15:03 ` Gao Xiang 2021-07-16 15:53 ` Andreas Grünbacher 2021-07-16 15:53 ` Andreas Grünbacher 2021-07-17 13:38 ` Gao Xiang 2021-07-17 13:38 ` Gao Xiang 2021-07-17 15:01 ` Matthew Wilcox 2021-07-17 15:15 ` Gao Xiang 2021-07-17 15:15 ` Gao Xiang 2021-07-17 18:40 ` Matthew Wilcox 2021-07-19 11:19 ` Christoph Hellwig 2021-07-19 11:19 ` Christoph Hellwig 2021-07-19 13:45 ` Gao Xiang 2021-07-19 13:45 ` Gao Xiang 2021-07-19 11:15 ` Christoph Hellwig 2021-07-19 13:31 ` Gao Xiang 2021-07-19 13:31 ` Gao Xiang 2021-07-16 5:07 ` [PATCH 2/2] erofs: convert all uncompressed cases to iomap Gao Xiang 2021-07-16 5:07 ` Gao Xiang 2021-07-18 5:30 ` kernel test robot 2021-07-18 5:30 ` [RFC PATCH] erofs: erofs_iomap_end() can be static kernel test robot 2021-07-18 16:53 ` 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=20210716050724.225041-1-hsiangkao@linux.alibaba.com \ --to=hsiangkao@linux.alibaba.com \ --cc=bo.liu@linux.alibaba.com \ --cc=chao@kernel.org \ --cc=djwong@kernel.org \ --cc=gerry@linux.alibaba.com \ --cc=hch@infradead.org \ --cc=joseph.qi@linux.alibaba.com \ --cc=linux-erofs@lists.ozlabs.org \ --cc=linux-fsdevel@vger.kernel.org \ --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: 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.