From: Eric Biggers <email@example.com> To: Lee Jones <firstname.lastname@example.org> Cc: Satya Tangirala <email@example.com>, "Theodore Y . Ts'o" <firstname.lastname@example.org>, Jaegeuk Kim <email@example.com>, Chao Yu <firstname.lastname@example.org>, Jens Axboe <email@example.com>, "Darrick J . Wong" <firstname.lastname@example.org>, open list <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Re: [PATCH v9 0/9] add support for direct I/O with fscrypt using blk-crypto Date: Thu, 22 Jul 2021 07:48:43 -0700 [thread overview] Message-ID: <YPmFSw4JbWnIozSZ@gmail.com> (raw) In-Reply-To: <CAF2Aj3h-Gt3bOxH4wXB7aeQ3jVzR3TEqd3uLsh4T9Q=e6W6iqQ@mail.gmail.com> Hi Lee, On Thu, Jul 22, 2021 at 12:23:47PM +0100, Lee Jones wrote: > > No review after 7 weeks on the list. > > Is there anything Satya can do to help expedite this please? > This series is basically ready, but I can't apply it because it depends on the other patch series "[PATCH v4 0/9] ensure bios aren't split in middle of crypto data unit" (https://email@example.com/T/#u). I will be re-reviewing that other patch series soon, but it primary needs review by the people who work more regularly with the block layer, and it will have to go in through the block tree (I can't apply it to the fscrypt tree). The original version of this series didn't require so many block layer changes, but it would have only allowed direct I/O with user buffer pointers aligned to the filesystem block size, which was too controversial with other filesystem developers; see the long discussion at https://firstname.lastname@example.org/T/#u. In addition, it was requested that we not add features to the "legacy" direct I/O implementation (fs/direct-io.c), so I have a patch series in progress "[PATCH 0/9] f2fs: use iomap for direct I/O" (https://email@example.com/T/#u) which will change f2fs to use iomap. Also please understand that Satya has left Google, so any further work from him on this is happening on a personal capacity in his free time. - Eric
next prev parent reply other threads:[~2021-07-22 14:48 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-04 21:08 Satya Tangirala 2021-06-04 21:09 ` [PATCH v9 1/9] block: blk-crypto-fallback: handle data unit split across multiple bvecs Satya Tangirala 2021-06-04 21:09 ` [PATCH v9 2/9] block: blk-crypto: relax alignment requirements for bvecs in bios Satya Tangirala 2021-06-04 21:09 ` [PATCH v9 3/9] fscrypt: add functions for direct I/O support Satya Tangirala 2021-07-23 20:42 ` Eric Biggers 2021-06-04 21:09 ` [PATCH v9 4/9] direct-io: add support for fscrypt using blk-crypto Satya Tangirala 2021-06-04 21:09 ` [PATCH v9 5/9] block: Make bio_iov_iter_get_pages() respect bio_required_sector_alignment() Satya Tangirala 2021-06-04 22:51 ` kernel test robot 2021-06-05 2:55 ` kernel test robot 2021-07-23 21:33 ` Eric Biggers 2021-07-24 7:19 ` Christoph Hellwig 2021-06-04 21:09 ` [PATCH v9 6/9] iomap: support direct I/O with fscrypt using blk-crypto Satya Tangirala 2021-07-22 19:04 ` Darrick J. Wong 2021-06-04 21:09 ` [PATCH v9 7/9] ext4: " Satya Tangirala 2021-06-04 21:09 ` [PATCH v9 8/9] f2fs: " Satya Tangirala 2021-06-04 21:09 ` [PATCH v9 9/9] fscrypt: update documentation for direct I/O support Satya Tangirala [not found] ` <CAF2Aj3h-Gt3bOxH4wXB7aeQ3jVzR3TEqd3uLsh4T9Q=e6W6iqQ@mail.gmail.com> 2021-07-22 14:48 ` Eric Biggers [this message] 2021-08-04 8:26 ` [PATCH v9 0/9] add support for direct I/O with fscrypt using blk-crypto Lee Jones
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=YPmFSw4JbWnIozSZ@gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v9 0/9] add support for direct I/O with fscrypt using blk-crypto' \ /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).