| /freebsd/sys/dev/drm2/ |
| H A D | drm_os_freebsd.c | 8 MALLOC_DEFINE(DRM_MEM_DMA, "drm_dma", "DRM DMA Data Structures");
9 MALLOC_DEFINE(DRM_MEM_SAREA, "drm_sarea", "DRM SAREA Data Structures");
10 MALLOC_DEFINE(DRM_MEM_DRIVER, "drm_driver", "DRM DRIVER Data Structures");
11 MALLOC_DEFINE(DRM_MEM_MAGIC, "drm_magic", "DRM MAGIC Data Structures");
12 MALLOC_DEFINE(DRM_MEM_MINOR, "drm_minor", "DRM MINOR Data Structures");
13 MALLOC_DEFINE(DRM_MEM_IOCTLS, "drm_ioctls", "DRM IOCTL Data Structures");
14 MALLOC_DEFINE(DRM_MEM_MAPS, "drm_maps", "DRM MAP Data Structures");
15 MALLOC_DEFINE(DRM_MEM_BUFS, "drm_bufs", "DRM BUFFER Data Structures");
16 MALLOC_DEFINE(DRM_MEM_SEGS, "drm_segs", "DRM SEGMENTS Data Structures");
17 MALLOC_DEFINE(DRM_MEM_PAGES, "drm_pages", "DRM PAGES Data Structures");
[all …]
|
| /freebsd/share/doc/smm/02.config/ |
| H A D | d.t | 38 Certain system data structures are sized at compile time
43 built-in limitations on certain data structures.
48 almost all data structures sized at compile time. This file
88 The number of ``file table'' structures. One file
98 The number of ``callout'' structures. One callout
108 The number of ``c-list'' structures. C-list structures are
123 The number of ``quota'' structures allocated. Quota structures
131 The number of ``dquot'' structures allocated. Dquot structures
153 the size of many data structures allocated at boot time because
161 The most important data structures sized at run-time are those used in
|
| /freebsd/contrib/libcbor/doc/source/ |
| H A D | api.rst | 15 …structures management by interacting directly with the decoder. Other clients might want to take c…
20 …coding and decoding *drivers*, routines that coordinate encoding and decoding of complex structures
21 - data structures to represent and transform CBOR structures
22 - routines for building and manipulating these structures
|
| /freebsd/lib/libc/gen/ |
| H A D | fts.3 | 74 returns a pointer to a linked list of structures, each of which describes
86 Two structures are defined (and typedef'd) in the include file
352 structures will require that the path buffer be modified using the
394 structures for the targets of symbolic links
398 structures
431 structures reference file characteristic information (the
449 structures for symbolic links themselves instead
453 structures for all symbolic links in the
475 structures for them.
490 structures as arguments and
[all …]
|
| /freebsd/share/man/man5/ |
| H A D | link.5 | 42 declares several structures that are present in dynamically linked
44 The structures define the interface between several components of the
47 structures within the binaries resembles the a.out format in many places
51 It also records a number of data structures
58 The collection of data structures described here will be referred to as the
98 is used to indicate the presence of the run-time linker structures.
109 .Sh DATA STRUCTURES
110 The data structures supporting dynamic linking and run-time relocation
196 structures
265 The run-time link-editor maintains a list of structures called
[all …]
|
| /freebsd/crypto/heimdal/doc/doxyout/hdb/html/ |
| H A D | annotated.html | 3 <title>Heimdalhdblibrary: Data Structures</title>
16 <li class="current"><a href="annotated.html"><span>Data Structures</span></a></li>
21 <li class="current"><a href="annotated.html"><span>Data Structures</span></a></li>
27 <h1>Data Structures</h1>Here are the data structures with brief descriptions:<table>
|
| /freebsd/crypto/heimdal/doc/doxyout/krb5/html/ |
| H A D | annotated.html | 3 <title>HeimdalKerberos5library: Data Structures</title>
18 <li class="current"><a href="annotated.html"><span>Data Structures</span></a></li>
23 <li class="current"><a href="annotated.html"><span>Data Structures</span></a></li>
28 <h1>Data Structures</h1>Here are the data structures with brief descriptions:<table>
|
| /freebsd/crypto/heimdal/doc/doxyout/ntlm/html/ |
| H A D | annotated.html | 3 <title>Heimdalntlmlibrary: Data Structures</title>
17 <li class="current"><a href="annotated.html"><span>Data Structures</span></a></li>
23 <li class="current"><a href="annotated.html"><span>Data Structures</span></a></li>
29 <h1>Data Structures</h1>Here are the data structures with brief descriptions:<table>
|
| /freebsd/contrib/elftoolchain/libelf/ |
| H A D | gelf.3 | 43 .Ss GElf Data Structures
44 The GElf API defines the following class-independent data structures:
83 These data structures are sized to be compatible with the
84 corresponding 64 bit ELF structures, and have the same internal
86 Class-dependent ELF structures are described in
131 .It "Allocating ELF Data Structures"
|
| H A D | gelf_update_ehdr.3 | 33 .Nd update underlying ELF data structures
45 These functions are used to update ELF data structures on the underlying
47 Class-dependent data structures in the underlying ELF descriptor
49 and the underlying ELF data structures are marked
|
| H A D | elf_flagdata.3 | 37 .Nd manipulate flags associated with ELF data structures
58 structures associated with an ELF file.
66 denote the data structures whose flags need to be changed.
146 will resynchronize the library's internal data structures.
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | ssl.pod | 38 =head1 DATA STRUCTURES
40 Here are some of the main data structures in the library.
61 B<SSL> structures which are later created for the connections.
73 links to mostly all other structures.
80 containing the prototypes for the data structures and functions:
|
| /freebsd/contrib/mandoc/ |
| H A D | mansearch.3 | 58 Returns a pointer to an array of result structures defined in
67 fields of all structures, as well as the
71 Returns the number of result structures contained in
89 structures, using the helper functions
|
| /freebsd/lib/libkvm/ |
| H A D | kvm_nlist.3 | 53 This argument points to an array of nlist structures, terminated by
84 structures,
89 These structures are similar to the nlist structures used by
|
| /freebsd/contrib/ofed/opensm/include/complib/ |
| H A D | cl_packon.h | 48 * The structure packing header files allow packing structures on byte
52 * between systems, as different platforms pad structures differently if
56 * packed structures that the alignment rules for all platforms are followed.
59 * include cl_packoff.h after the structure definition. Multiple structures
|
| /freebsd/lib/libsys/ |
| H A D | getfsstat.2 | 52 structures, as described in
58 structures, one for each mounted file system
65 can hold, not the count of statfs structures it will hold.
93 structures is returned.
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | CRYPTO_get_ex_new_index.pod | 43 Several OpenSSL structures can have application-specific data attached to them,
45 The specific structures are:
67 applications to use this facility for their own structures.
70 structures. Since the application data can be anything at all it is passed
78 unique within structures for the lifetime of the program. Applications
141 are pointers to the destination and source B<CRYPTO_EX_DATA> structures,
|
| /freebsd/contrib/libcbor/doc/source/api/ |
| H A D | decoding.rst | 36 (PSD = Provided Data Structures, CDS = Custom Data Structures)
43 Associated data structures
|
| /freebsd/sys/netgraph/ |
| H A D | ng_tag.c | 84 * We still keep API structures in memory to simplify access to them for
87 * accessed from API structures, there would be double pointer dereferencing
256 * This are default API structures (initialized to zeroes) which are
258 * One could ask why to have this structures at all when we have
259 * ng_tag_hookinfo initialized to zero and don't need in and out structures
262 * this default structures and initialize thisHook once at hook creation
314 * structures, so we need to set explicitly only thisHook field in ng_tag_newhook()
315 * in that structures (after allocating them, of course). in ng_tag_newhook()
333 * response to messages requesting API structures with data who in ng_tag_newhook()
533 * creation in default structures). in ng_tag_rcvdata()
[all …]
|
| /freebsd/sys/fs/nfs/ |
| H A D | nfsrvstate.h | 158 * To add/delete one of these structures from the lists, you must lock
194 * it makes cleanup, etc. simpler. These structures are used in four ways:
195 * - open_owner structures chained off of nfsclient
196 * - open file structures chained off an open_owner structure
197 * - lock_owner structures chained off an open file structure
198 * - delegated file structures chained off of nfsclient and nfslockfile
202 * If it is a lockowner stateid, nfslock structures hang off it.
251 * nfslockfile (the file) structures, for the file and owner it
326 * These structures are used for the stable storage restart stuff.
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | ssl.7 | 170 .SH "DATA STRUCTURES"
171 .IX Header "DATA STRUCTURES"
172 Here are some of the main data structures in the library.
188 \&\fB\s-1SSL\s0\fR structures which are later created for the connections.
198 links to mostly all other structures.
202 containing the prototypes for the data structures and functions:
|
| /freebsd/share/man/man9/ |
| H A D | ieee80211.9 | 130 structures associated with the driver, and performs Ethernet and BPF
217 .Sh DATA STRUCTURES
222 structures.
223 Drivers are expected to setup various shared state in these structures
241 This technique of giving the driver control to allocate data structures
244 data structures and should be exploited to maintain driver-private state
249 The other main data structures are the station, or node, table
264 structures also hold a collection of method pointers that drivers
276 data structures before passing control.
502 all associated vaps and ifnet structures are reclaimed or inaccessible
|
| /freebsd/share/doc/psd/24.xdr/ |
| H A D | xdr.nts.ms | 22 that allow a C programmer to describe arbitrary data structures in a
247 data structures present portability problems, particularly with
299 structures whether or not conversion is required. In networking
314 structures, unions, and arrays, to name a few.
317 to describe arbitrary data structures,
319 or objects pointed at from other structures.
320 The structures themselves may contain arrays of arbitrary elements,
321 or pointers to other structures.
399 but its value becomes obvious when nontrivial data structures
632 strings, arrays, unions, and pointers to structures.
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | CRYPTO_get_ex_new_index.3 | 178 Several OpenSSL structures can have application-specific data attached to them,
180 The specific structures are:
204 applications to use this facility for their own structures.
207 structures. Since the application data can be anything at all it is passed
215 unique within structures for the lifetime of the program. Applications
277 are pointers to the destination and source \fB\s-1CRYPTO_EX_DATA\s0\fR structures,
|
| /freebsd/share/doc/smm/18.net/ |
| H A D | 3.t | 37 information to be ``hidden'' in common data structures which
41 the use of shared data structures to those kept by a suite of
53 data structures they manipulate.
|