HomeSort by: relevance | last modified time | path
    Searched refs:nopwrite (Results 1 - 3 of 3) sorted by relevancy

  /src/external/cddl/osnet/dist/uts/common/fs/zfs/sys/
zio.h 532 boolean_t nopwrite);
  /src/external/cddl/osnet/dist/uts/common/fs/zfs/
dmu.c 56 * Enable/disable nopwrite feature.
61 &zfs_nopwrite_enabled, 0, "Enable nopwrite feature");
1877 * We usually want to perform a nopwrite if X and Z are the
1879 * change before this write takes effect), then a nopwrite will
1887 * Therefore, we disable nopwrite if the current BP could change
2004 boolean_t nopwrite = B_FALSE; local
2082 * Enable nopwrite if we have secure enough checksum
2084 * compression is enabled. We don't enable nopwrite if
2088 nopwrite = (!dedup && (zio_checksum_table[checksum].ci_flags &
2100 zp->zp_nopwrite = nopwrite;
    [all...]
zio.c 889 zio_write_override(zio_t *zio, blkptr_t *bp, int copies, boolean_t nopwrite)
899 * that nopwrite and dedup are mutually exclusive.
901 zio->io_prop.zp_dedup = nopwrite ? B_FALSE : zio->io_prop.zp_dedup;
902 zio->io_prop.zp_nopwrite = nopwrite;
1277 * If we've been overridden and nopwrite is set then
1278 * set the flag accordingly to indicate that a nopwrite
2325 * new bp is necessary. The nopwrite feature can handle writes in
2334 * (malicious) collisions. To trigger a nopwrite, you have to be able
2336 * collision) nopwrite is no worse than simply writing to the file.
2338 * used for nopwrite, assuming that the salt and the checksum
    [all...]

Completed in 87 milliseconds