Home
last modified time | relevance | path

Searched refs:META (Results 1 – 11 of 11) sorted by relevance

/f-stack/freebsd/amd64/include/
H A Dvmm_snapshot.h112 #define SNAPSHOT_BUF_OR_LEAVE(DATA, LEN, META, RES, LABEL) \ argument
114 (RES) = vm_snapshot_buf((DATA), (LEN), (META)); \
116 vm_snapshot_buf_err(#DATA, (META)->op); \
121 #define SNAPSHOT_VAR_OR_LEAVE(DATA, META, RES, LABEL) \ argument
122 SNAPSHOT_BUF_OR_LEAVE(&(DATA), sizeof(DATA), (META), (RES), LABEL)
133 (META)); \
143 #define SNAPSHOT_BUF_CMP_OR_LEAVE(DATA, LEN, META, RES, LABEL) \ argument
145 (RES) = vm_snapshot_buf_cmp((DATA), (LEN), (META)); \
147 vm_snapshot_buf_err(#DATA, (META)->op); \
152 #define SNAPSHOT_VAR_CMP_OR_LEAVE(DATA, META, RES, LABEL) \ argument
[all …]
/f-stack/freebsd/contrib/openzfs/config/
H A Dzfs-meta.m43 dnl # Read meta data from the META file. When building from a git repository
8 dnl # The META file format is as follows:
27 dnl # The following META keys are recognized:
48 META="$srcdir/META"
50 if test -f "$META"; then
51 _zfs_ac_meta_type="META file"
195 dnl # Returns the META VALUE associated with the given KEY_NAME_OR_REGEX expr.
203 dnl # whereas the "$1" will undergo M4 parameter expansion for the META key.
206 [`$AWK -F ':@<:@ \t@:>@+' '$[]1 ~ /^ *$1$/ { print $[]2; exit }' $META`]dnl
/f-stack/freebsd/contrib/openzfs/
H A DREADME.md34 * The `META` file contains the officially recognized supported Linux kernel versions.
H A DMakefile.am30 EXTRA_DIST += META AUTHORS COPYRIGHT LICENSE NEWS NOTICE README.md
83 $(distdir)/META
H A Dconfigure.ac33 AC_INIT(m4_esyscmd(grep ^Name: META | cut -d ':' -f 2 | tr -d ' \n'),
34 m4_esyscmd(grep ^Version: META | cut -d ':' -f 2 | tr -d ' \n'))
/f-stack/freebsd/sys/
H A Dkbio.h159 #define META 0x84 /* meta key */ macro
/f-stack/dpdk/doc/guides/nics/
H A Dmlx5.rst788 ``MARK`` and ``META`` item of ``rte_flow``. The newly introduced
794 ``META`` related actions and items operate only within NIC Tx and
795 NIC Rx steering domains, no ``MARK`` and ``META`` information crosses
796 the domain boundaries. The ``MARK`` item is 24 bits wide, the ``META``
799 - 1, this engages extensive metadata mode, the ``MARK`` and ``META``
801 including FDB, ``MARK`` and ``META`` information may cross the domain
802 boundaries. The ``MARK`` item is 24 bits wide, the ``META`` item width
804 32 bits. Within NIC Tx domain ``META`` data width is 32 bits for
810 - 2, this engages extensive metadata mode, the ``MARK`` and ``META``
812 including FDB, ``MARK`` and ``META`` information may cross the domain
[all …]
/f-stack/dpdk/doc/guides/howto/
H A Ddebug_troubleshoot.rst441 to META data error flags. Dumping private meta-data in the objects can give
/f-stack/dpdk/lib/librte_ethdev/
H A Drte_flow.c85 MK_FLOW_ITEM(META, sizeof(struct rte_flow_item_meta)),
/f-stack/dpdk/doc/guides/prog_guide/
H A Drte_flow.rst689 Item: ``META``
703 .. table:: META
1295 Item: ``META``
2615 Set metadata. Item ``META`` matches metadata.
/f-stack/dpdk/app/test-pmd/
H A Dcmdline_flow.c2985 .priv = PRIV_ITEM(META, sizeof(struct rte_flow_item_meta)),