From: "Matthew Wilcox (Oracle)" <email@example.com> To: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Cc: "Matthew Wilcox \(Oracle\)" <email@example.com> Subject: [PATCH 0/2] iomap: make inline data support more flexible Date: Sat, 24 Jul 2021 04:44:33 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) The first patch seems to be where Gao Xiang, Christoph and I have settled for immediate support of EROFS tails. The second is a prequel to the folio work. Because folios are variable size, if we have, eg, an 8.1KiB file, we must support reading the first two pages of the folio from blocks and then the last 100 bytes from the tailpack. That means effectively supporting block size < page size. I thought it cleaner to separate it out, and maybe that can go in this round. The folio patches are rebased on top of all this; if you're hungry to see them, they can be found at https://git.infradead.org/users/willy/pagecache.git/shortlog/refs/heads/folio as usual. I haven't applied all the R-b yet (and I should probably figure out which ones still apply since I did some substantial changes to a couple of the patches). Gao Xiang (1): iomap: Support file tail packing Matthew Wilcox (Oracle) (1): iomap: Support inline data with block size < page size fs/iomap/buffered-io.c | 46 +++++++++++++++++++++++++----------------- fs/iomap/direct-io.c | 10 +++++---- include/linux/iomap.h | 14 +++++++++++++ 3 files changed, 47 insertions(+), 23 deletions(-) -- 2.30.2
next reply other threads:[~2021-07-24 3:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-24 3:44 Matthew Wilcox (Oracle) [this message] 2021-07-24 3:44 ` [PATCH 1/2] iomap: Support file tail packing Matthew Wilcox (Oracle) 2021-07-24 3:44 ` [PATCH 2/2] iomap: Support inline data with block size < page size Matthew Wilcox (Oracle) 2021-07-24 4:46 ` Gao Xiang 2021-07-24 5:11 ` Gao Xiang 2021-07-24 7:52 ` Gao Xiang 2021-07-24 14:03 ` Matthew Wilcox 2021-07-24 15:14 ` 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH 0/2] iomap: make inline data support more flexible' \ /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
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).