Home
last modified time | relevance | path

Searched refs:backing (Results 1 – 25 of 30) sorted by relevance

12

/freebsd/sys/ufs/ufs/
H A DREADME.extattr14 backing file, in the style of the quota implementation, meaning that it
39 system. The extattrctl utility may be used to initialize backing files
54 [attrfile] argument specifies the attribute backing file to use. When
55 using the "initattr" function to initialize a backing file, the maximum
59 creating a sparse backing file. This prevents attribute operations from
78 directory for any potential backing files, and enable an EA for each valid
79 backing file with the name of the backing file as the attribute name.
H A DREADME.acls68 commands may be used to create the necessary EA backing files for
/freebsd/sys/dev/virtio/gpu/
H A Dvirtio_gpu.c563 struct virtio_gpu_resource_attach_backing backing; in vtgpu_attach_backing() member
571 s.req.backing.hdr.type = in vtgpu_attach_backing()
573 s.req.backing.hdr.flags = htole32(VIRTIO_GPU_FLAG_FENCE); in vtgpu_attach_backing()
574 s.req.backing.hdr.fence_id = htole64( in vtgpu_attach_backing()
577 s.req.backing.resource_id = htole32(VTGPU_RESOURCE_ID); in vtgpu_attach_backing()
578 s.req.backing.nr_entries = htole32(1); in vtgpu_attach_backing()
/freebsd/sys/cam/ctl/
H A DREADME.ctl.txt41 - Support for multiple simultaneous backing stores
114 - You can see the LUN type and backing store for block/file backend LUNs
198 - The block backend can now send multiple I/Os to backing files. Multiple
203 There are some restrictions when the backing device is a block device,
213 or block devices as a backing store.
233 optimal solution for backing targets served by CTL with ZFS would be to
297 backing store for a LUN. Multiple threads are started to do I/O to the
298 backing device, primarily because the VFS API requires that to get any
/freebsd/contrib/file/magic/Magdir/
H A Dvirtual235 >>12 belong >0 \b, has backing file (
242 # Really useful if you want to know if your backing
257 >>8 bequad >0 \b, has backing file
262 # the file is over 4G, and the backing file path is stored after the first 4G,
272 >>8 bequad >0 \b, has backing file
277 # the file is over 4G, and the backing file path is stored after the first 4G,
H A Dlinux375 >>8 string >\0 \b, backing file %s
377 >>32 string >\0 \b, backing file %s
729 # BCache backing and cache devices
734 >>0x1010 ulequad 1 backing device
736 >>0x1010 ulequad 4 backing device
/freebsd/contrib/lutok/
H A DNEWS23 of arguments to the loaded chunks and an error handler to the backing
/freebsd/sys/contrib/device-tree/Bindings/soc/fsl/
H A Dbman.txt67 BMan requires a contiguous range of physical memory used for the backing store
H A Dqman.txt81 QMan requires two contiguous range of physical memory used for the backing store
/freebsd/sys/contrib/openzfs/config/
H A Dkernel-blk-queue.m455 #include <linux/backing-dev.h>
/freebsd/contrib/llvm-project/llvm/lib/Support/Unix/
H A DMemory.inc81 // page without file backing, but we need a fallback of opening /dev/zero
H A DThreading.inc275 // significant time to complete. Examples include indexing, backing up, or
/freebsd/contrib/llvm-project/lldb/docs/design/
H A Dsbapi.rst
/freebsd/crypto/openssl/crypto/
H A Dsparccpuid.S29 ! This routine wipes registers, but not the backing store [which
/freebsd/contrib/flex/
H A DONEWS504 backing-up states only if you remove *all* of them.
786 - The term "backtracking" has been renamed "backing up",
811 - The example of backing-up in flexdoc was erroneous; it
H A DChangeLog8154 * gen.c: fixed bug in needing yy_cp for -Cf w/ backing up
8478 * gen.c: fixed bug in adjusting yytext before backing up
9589 * flexdef.h: Removed a lot of #ifdef chud "backtracking" -> "backing
9594 * main.c: "backtracking" -> "backing up" got rid of time reports
9598 * gen.c: "backtracking" -> "backing up" some portability tweaks
9620 * dfa.c: "backtracking" -> "backing up"
/freebsd/sys/kern/
H A Dsys_pipe.c239 static int pipe_create(struct pipe *pipe, bool backing);
/freebsd/contrib/ncurses/
H A DANNOUNCE427 + the panel library, supporting a stack of windows with backing
/freebsd/contrib/flex/src/
H A Dflex.skl524 * possible backing-up.
1741 %% [17.0] code to find the next state, and perhaps do backing up, goes here
/freebsd/contrib/llvm-project/llvm/lib/Target/AMDGPU/
H A DAMDGPU.td1052 "Hardware supports backing off s_barrier if an exception occurs"
/freebsd/contrib/llvm-project/clang/include/clang/Basic/
H A DDiagnosticSemaKinds.td10094 "%select{reference|backing array for 'std::initializer_list'}2 "
10100 "%select{reference|backing array for 'std::initializer_list'}2 "
10118 "array backing "
10128 "object backing the pointer "
10131 def warn_dangling_lifetime_pointer_assignment : Warning<"object backing the "
10135 "array backing "
10141 "object backing the pointer %0 "
10147 "%select{temporary|backing array of initializer list}0 created "
10149 "is not yet supported; lifetime of %select{temporary|backing array}0 "
/freebsd/contrib/jemalloc/
H A DChangeLog1544 multiple threads raced to create a new run of backing pages.
/freebsd/contrib/unbound/contrib/
H A Dfastrpz.patch652 + * and retransmit its configuration, backing off as usual if anything
/freebsd/contrib/ncurses/doc/
H A Dncurses-intro.doc201 associate backing store with each of a stack or deck of overlapping
/freebsd/contrib/diff/
H A DChangeLog3804 * io.c (find_and_hash_lines): When backing up over starting context,

12