On Thu, 10 Aug 2023 23:27:07 -0700, Hugh Dickins wrote: > Depending upon your philosophical viewpoint, either tmpfs always does > direct IO, or it cannot ever do direct IO; but whichever, if tmpfs is to > stand in for a more sophisticated filesystem, it can be helpful for tmpfs > to support O_DIRECT. So, give tmpfs a shmem_file_open() method, to set > the FMODE_CAN_ODIRECT flag: then unchanged shmem_file_read_iter() and new > shmem_file_write_iter() do the work (without any shmem_direct_IO() stub). > > [...] I've dropped the previous version and applied this one. Thank! --- Applied to the vfs.tmpfs branch of the vfs/vfs.git tree. Patches in the vfs.tmpfs branch should appear in linux-next soon. Please report any outstanding bugs that were missed during review in a new review to the original patch series allowing us to drop it. It's encouraged to provide Acked-bys and Reviewed-bys even though the patch has now been applied. If possible patch trailers will be updated. Note that commit hashes shown below are subject to change due to rebase, trailer updates or similar. If in doubt, please check the listed branch. tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git branch: vfs.tmpfs [4/5] tmpfs: trivial support for direct IO https://git.kernel.org/vfs/vfs/c/6b55d273ec5b
