mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2024-12-26 19:19:32 +03:00
a584ef2605
Direct IO via the O_DIRECT flag was originally introduced in XFS by
IRIX for database workloads. Its purpose was to allow the database
to bypass the page and buffer caches to prevent unnecessary IO
operations (e.g. readahead) while preventing contention for system
memory between the database and kernel caches.
On Illumos, there is a library function called directio(3C) that
allows user space to provide a hint to the file system that Direct IO
is useful, but the file system is free to ignore it. The semantics
are also entirely a file system decision. Those that do not
implement it return ENOTTY.
Since the semantics were never defined in any standard, O_DIRECT is
implemented such that it conforms to the behavior described in the
Linux open(2) man page as follows.
1. Minimize cache effects of the I/O.
By design the ARC is already scan-resistant which helps mitigate
the need for special O_DIRECT handling. Data which is only
accessed once will be the first to be evicted from the cache.
This behavior is in consistent with Illumos and FreeBSD.
Future performance work may wish to investigate the benefits of
immediately evicting data from the cache which has been read or
written with the O_DIRECT flag. Functionally this behavior is
very similar to applying the 'primarycache=metadata' property
per open file.
2. O_DIRECT _MAY_ impose restrictions on IO alignment and length.
No additional alignment or length restrictions are imposed.
3. O_DIRECT _MAY_ perform unbuffered IO operations directly
between user memory and block device.
No unbuffered IO operations are currently supported. In order
to support features such as transparent compression, encryption,
and checksumming a copy must be made to transform the data.
4. O_DIRECT _MAY_ imply O_DSYNC (XFS).
O_DIRECT does not imply O_DSYNC for ZFS. Callers must provide
O_DSYNC to request synchronous semantics.
5. O_DIRECT _MAY_ disable file locking that serializes IO
operations. Applications should avoid mixing O_DIRECT
and normal IO or mmap(2) IO to the same file. This is
particularly true for overlapping regions.
All I/O in ZFS is locked for correctness and this locking is not
disabled by O_DIRECT. However, concurrently mixing O_DIRECT,
mmap(2), and normal I/O on the same file is not recommended.
This change is implemented by layering the aops->direct_IO operations
on the existing AIO operations. Code already existed in ZFS on Linux
for bypassing the page cache when O_DIRECT is specified.
References:
* http://xfs.org/docs/xfsdocs-xml-dev/XFS_User_Guide/tmp/en-US/html/ch02s09.html
* https://blogs.oracle.com/roch/entry/zfs_and_directio
* https://ext4.wiki.kernel.org/index.php/Clarifying_Direct_IO's_Semantics
* https://illumos.org/man/3c/directio
Reviewed-by: Richard Elling <Richard.Elling@RichardElling.com>
Signed-off-by: Richard Yao <ryao@gentoo.org>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #224
Closes #7823
131 lines
3.0 KiB
Plaintext
131 lines
3.0 KiB
Plaintext
dnl #
|
|
dnl # Linux 4.6.x API change
|
|
dnl #
|
|
AC_DEFUN([ZFS_AC_KERNEL_VFS_DIRECT_IO_ITER], [
|
|
AC_MSG_CHECKING([whether aops->direct_IO() uses iov_iter])
|
|
ZFS_LINUX_TRY_COMPILE([
|
|
#include <linux/fs.h>
|
|
|
|
ssize_t test_direct_IO(struct kiocb *kiocb,
|
|
struct iov_iter *iter) { return 0; }
|
|
|
|
static const struct address_space_operations
|
|
aops __attribute__ ((unused)) = {
|
|
.direct_IO = test_direct_IO,
|
|
};
|
|
],[
|
|
],[
|
|
AC_MSG_RESULT([yes])
|
|
AC_DEFINE(HAVE_VFS_DIRECT_IO_ITER, 1,
|
|
[aops->direct_IO() uses iov_iter without rw])
|
|
zfs_ac_direct_io="yes"
|
|
],[
|
|
AC_MSG_RESULT([no])
|
|
])
|
|
])
|
|
|
|
dnl #
|
|
dnl # Linux 4.1.x API change
|
|
dnl #
|
|
AC_DEFUN([ZFS_AC_KERNEL_VFS_DIRECT_IO_ITER_OFFSET], [
|
|
AC_MSG_CHECKING(
|
|
[whether aops->direct_IO() uses iov_iter with offset])
|
|
ZFS_LINUX_TRY_COMPILE([
|
|
#include <linux/fs.h>
|
|
|
|
ssize_t test_direct_IO(struct kiocb *kiocb,
|
|
struct iov_iter *iter, loff_t offset) { return 0; }
|
|
|
|
static const struct address_space_operations
|
|
aops __attribute__ ((unused)) = {
|
|
.direct_IO = test_direct_IO,
|
|
};
|
|
],[
|
|
],[
|
|
AC_MSG_RESULT([yes])
|
|
AC_DEFINE(HAVE_VFS_DIRECT_IO_ITER_OFFSET, 1,
|
|
[aops->direct_IO() uses iov_iter with offset])
|
|
zfs_ac_direct_io="yes"
|
|
],[
|
|
AC_MSG_RESULT([no])
|
|
])
|
|
])
|
|
|
|
dnl #
|
|
dnl # Linux 3.16.x API change
|
|
dnl #
|
|
AC_DEFUN([ZFS_AC_KERNEL_VFS_DIRECT_IO_ITER_RW_OFFSET], [
|
|
AC_MSG_CHECKING(
|
|
[whether aops->direct_IO() uses iov_iter with rw and offset])
|
|
ZFS_LINUX_TRY_COMPILE([
|
|
#include <linux/fs.h>
|
|
|
|
ssize_t test_direct_IO(int rw, struct kiocb *kiocb,
|
|
struct iov_iter *iter, loff_t offset) { return 0; }
|
|
|
|
static const struct address_space_operations
|
|
aops __attribute__ ((unused)) = {
|
|
.direct_IO = test_direct_IO,
|
|
};
|
|
],[
|
|
],[
|
|
AC_MSG_RESULT([yes])
|
|
AC_DEFINE(HAVE_VFS_DIRECT_IO_ITER_RW_OFFSET, 1,
|
|
[aops->direct_IO() uses iov_iter with rw and offset])
|
|
zfs_ac_direct_io="yes"
|
|
],[
|
|
AC_MSG_RESULT([no])
|
|
])
|
|
])
|
|
|
|
dnl #
|
|
dnl # Ancient Linux API (predates git)
|
|
dnl #
|
|
AC_DEFUN([ZFS_AC_KERNEL_VFS_DIRECT_IO_IOVEC], [
|
|
AC_MSG_CHECKING([whether aops->direct_IO() uses iovec])
|
|
ZFS_LINUX_TRY_COMPILE([
|
|
#include <linux/fs.h>
|
|
|
|
ssize_t test_direct_IO(int rw, struct kiocb *kiocb,
|
|
const struct iovec *iov, loff_t offset,
|
|
unsigned long nr_segs) { return 0; }
|
|
|
|
static const struct address_space_operations
|
|
aops __attribute__ ((unused)) = {
|
|
.direct_IO = test_direct_IO,
|
|
};
|
|
],[
|
|
],[
|
|
AC_MSG_RESULT([yes])
|
|
AC_DEFINE(HAVE_VFS_DIRECT_IO_IOVEC, 1,
|
|
[aops->direct_IO() uses iovec])
|
|
zfs_ac_direct_io="yes"
|
|
],[
|
|
AC_MSG_RESULT([no])
|
|
])
|
|
])
|
|
|
|
AC_DEFUN([ZFS_AC_KERNEL_VFS_DIRECT_IO], [
|
|
zfs_ac_direct_io="no"
|
|
|
|
if test "$zfs_ac_direct_io" = "no"; then
|
|
ZFS_AC_KERNEL_VFS_DIRECT_IO_ITER
|
|
fi
|
|
|
|
if test "$zfs_ac_direct_io" = "no"; then
|
|
ZFS_AC_KERNEL_VFS_DIRECT_IO_ITER_OFFSET
|
|
fi
|
|
|
|
if test "$zfs_ac_direct_io" = "no"; then
|
|
ZFS_AC_KERNEL_VFS_DIRECT_IO_ITER_RW_OFFSET
|
|
fi
|
|
|
|
if test "$zfs_ac_direct_io" = "no"; then
|
|
ZFS_AC_KERNEL_VFS_DIRECT_IO_IOVEC
|
|
fi
|
|
|
|
if test "$zfs_ac_direct_io" = "no"; then
|
|
AC_MSG_ERROR([no; unknown direct IO interface])
|
|
fi
|
|
])
|