diff options
| author | Alexander Motin <[email protected]> | 2020-10-30 11:50:57 -0400 |
|---|---|---|
| committer | GitHub <[email protected]> | 2020-10-30 08:50:57 -0700 |
| commit | e3a6ac8d06210ac035cec8d86fab05549ff54f94 (patch) | |
| tree | 2ff624e42ef5a04fc8a75d10d5477eb90907ba2a /module/os | |
| parent | f829227f49117c4466bab88e90c187b273211c5f (diff) | |
FreeBSD: Remove BIO_ORDERED flag from BIO_FLUSH
ZFS always waits for the write completion before flushing the cache.
That is why it does not require explicit ordering fences around it,
which are pretty difficult to implement for NVMe, since one has no
internal concept of strict request ordering.
This was already removed from FreeBSD once, but got resurrected
by mistake during OpenZFS merge.
Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Ryan Moeller <[email protected]>
Signed-off-by: Alexander Motin <[email protected]>
Closes #11130
Diffstat (limited to 'module/os')
| -rw-r--r-- | module/os/freebsd/zfs/vdev_geom.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/module/os/freebsd/zfs/vdev_geom.c b/module/os/freebsd/zfs/vdev_geom.c index bf06f6919..b888cfdf0 100644 --- a/module/os/freebsd/zfs/vdev_geom.c +++ b/module/os/freebsd/zfs/vdev_geom.c @@ -1141,7 +1141,6 @@ sendreq: break; case ZIO_TYPE_IOCTL: bp->bio_cmd = BIO_FLUSH; - bp->bio_flags |= BIO_ORDERED; bp->bio_data = NULL; bp->bio_offset = cp->provider->mediasize; bp->bio_length = 0; |