Home
last modified time | relevance | path

Searched full:dmu (Results 1 – 25 of 156) sorted by relevance

1234567

/freebsd/sys/contrib/device-tree/Bindings/phy/
H A Dbcm-ns-usb2-phy.txt5 - reg: iomem address range of DMU (Device Management Unit)
6 - reg-names: "dmu", the only needed & supported reg right now
17 reg-names = "dmu";
H A Dbcm-ns-usb2-phy.yaml25 description: iomem address range of DMU (Device Management Unit)
30 - const: dmu
/freebsd/sys/contrib/openzfs/include/sys/
H A Ddmu_tx.h33 #include <sys/dmu.h>
116 * Used for dmu tx kstat.
142 * These routines are defined in dmu.h, and are called by the user.
158 * These routines are only called by the DMU.
H A Dzap.h34 * The ZAP is a module which sits on top of the DMU (Data Management
35 * Unit) and implements a higher-level storage primitive using DMU
38 * A "zapobj" is a DMU object which the ZAP uses to stores attributes.
40 * not access the DMU object directly using DMU routines.
48 * (object number) of another dmu object (which may be itself a zapobj).
53 * DMU's restriction that a transaction may not be operated on
84 #include <sys/dmu.h>
H A Ddmu.h39 * This file describes the interface that the DMU provides for its
42 * The DMU also interacts with the SPA. That interface is described in
185 /* dmu: */
566 * Obtain the DMU buffer from the specified object which contains the
570 * what you hold. You must have a hold on any dmu_buf_t* you pass to the DMU.
595 * Add a reference to a dmu buffer that has already been held via
601 * Attempt to add a reference to a dmu buffer that is in an unknown state,
615 * dmu_buf_hold_array holds the DMU buffers which contain all bytes in a
632 * A DMU buffer user object may be associated with a dbuf for the
644 * with a simple cast. Since the DMU buf user API never needs access
[all …]
H A Ddsl_prop.h30 #include <sys/dmu.h>
42 /* The callback func may not call into the DMU or DSL! */
H A Dzfs_sa.h32 #include <sys/dmu.h>
110 uint64_t zp_xattr; /* 104 - DMU object for xattrs */
H A Dzfs_quota.h25 #include <sys/dmu.h>
H A Dzfs_stat.h31 #include <sys/dmu.h>
H A Dvdev_indirect_births.h23 #include <sys/dmu.h>
H A Dbrt.h32 #include <sys/dmu.h>
H A Ddataset_kstats.h31 #include <sys/dmu.h>
H A Ddsl_deleg.h29 #include <sys/dmu.h>
/freebsd/sys/contrib/device-tree/Bindings/clock/st/
H A Dst,flexgen.txt107 "clk-rx-icn-dmu",
110 "clk-tx-icn-dmu",
117 "clk-pp-dmu",
118 "clk-vid-dmu",
122 "clk-st231-dmu",
/freebsd/crypto/openssl/test/recipes/20-test_dhparam_check_data/valid/
H A Ddhx_p1024_q160_t1864.pem7 cf4XMul9XE+dMU/mpeUuWgjcuVnRqIVq5JUsAhUArW8on8uZ0Tob8bb0LBXnLGBR
/freebsd/sys/contrib/openzfs/cmd/
H A Darc_summary33 the Data Management Unit (DMU), Virtual Devices (VDEVs), and tunables. See
59 SECTIONS = 'arc archits dmu l2arc spl tunables vdev zil'.split()
65 'dmu': 'dmu_tx',
818 """Collect information on the DMU"""
826 prt_1('DMU predictive prefetcher calls:', f_hits(zfetch_access_total))
1008 'dmu': section_dmu,
1045 4: 'dmu',
/freebsd/sys/contrib/device-tree/Bindings/thermal/
H A Dbrcm,ns-thermal.txt3 This binding describes thermal sensor that is part of Northstar's DMU (Device
H A Dbrcm,ns-thermal.yaml13 Thermal sensor that is part of Northstar's DMU (Device Management Unit).
/freebsd/sys/contrib/device-tree/Bindings/pinctrl/
H A Dbrcm,bcm4708-pinmux.txt35 dmu@1800c000 {
/freebsd/sys/contrib/openzfs/contrib/debian/
H A Dcontrol.modules.in28 Includes the SPA, DMU, ZVOL, and ZPL components of OpenZFS.
/freebsd/sys/contrib/openzfs/include/os/freebsd/zfs/sys/
H A Dzfs_vfsops_os.h175 * currently defined and imposed by the DMU.
197 * the limits currently defined and imposed by the DMU.
H A Dzfs_dir.h30 #include <sys/dmu.h>
/freebsd/sys/contrib/openzfs/include/os/linux/zfs/sys/
H A Dzfs_vfsops_os.h195 * currently defined and imposed by the DMU.
217 * the limits currently defined and imposed by the DMU.
/freebsd/sys/contrib/openzfs/cmd/zstream/
H A Dzstream_token.c44 #include <sys/dmu.h>
/freebsd/sys/contrib/openzfs/module/os/freebsd/zfs/
H A Dhkdf.c20 #include <sys/dmu.h>

1234567