Home
last modified time | relevance | path

Searched full:structures (Results 1 – 25 of 2577) sorted by relevance

12345678910>>...104

/illumos-gate/usr/src/man/man9s/
H A DIntro.9s19 .Nd introduction to kernel data structures
21 Section 9S describes the data structures that are used by the kernel and
27 The structures listed here have varying ABI guarantees.
28 While the majority of structures documented here are part of committed
30 Uncommitted structures have no ABI guarantees and may change at any
34 The rest of this manual groups documented structures into categories
37 The structures here are all fundamental to initializing a device driver.
43 These structures are generally required for every kernel module.
50 These structures are used as part of the fundamental units of performing
62 .Ss Message Block Structures
[all …]
/illumos-gate/usr/src/boot/efi/include/Protocol/
H A DKms.h235 /// EFI_KMS_KEY_DESCRIPTOR structures.
279 /// An array of EFI_KMS_DYNAMIC_FIELD structures.
328 /// called with multiple EFI_KMS_KEY_ATTRIBUTE structures.
427 structures which describe the keys to be generated.
494 @retval EFI_NOT_FOUND One or more EFI_KMS_KEY_DESCRIPTOR structures
496 contains the number of structures which were successfully
497 processed. Individual structures will reflect the status of the
522 structures which describe the keys to be retrieved
569 KeyValue buffer does not contain enough structures
571 the available structures will be filled and
[all …]
H A DSimpleFileSystem.h50 @retval EFI_VOLUME_CORRUPTED The file system structures are corrupted.
105 @retval EFI_VOLUME_CORRUPTED The file system structures are corrupted.
186 @retval EFI_VOLUME_CORRUPTED The file system structures are corrupted.
214 @retval EFI_VOLUME_CORRUPTED The file system structures are corrupted.
282 @retval EFI_VOLUME_CORRUPTED The file system structures are corrupted.
310 @retval EFI_VOLUME_CORRUPTED The file system structures are corrupted.
348 @retval EFI_VOLUME_CORRUPTED The file system structures are corrupted.
418 @retval EFI_VOLUME_CORRUPTED The file system structures are corrupted.
450 @retval EFI_VOLUME_CORRUPTED The file system structures are corrupted.
473 @retval EFI_VOLUME_CORRUPTED The file system structures are corrupted.
[all …]
/illumos-gate/usr/src/man/man3c/
H A Dfts.3c78 returns a pointer to a linked list of structures, each of which describes
95 Two structures are defined
356 structures will require that the path buffer be modified using the
399 structures for the targets of symbolic links
403 structures
433 structures reference file characteristic information
454 structures for symbolic links themselves instead
458 structures for all symbolic links in the
480 structures for them.
496 structures as arguments and
[all …]
/illumos-gate/usr/src/cmd/filesync/
H A DREADME33 Primary Data Structures
36 data structures major structures and their contents
85 Primary Data Structures
130 data structures:
132 there is an ordered list of "base" structures
164 list. This is an ordered list of "file" structures which
217 data-structures for recording rules
218 data-structures for recording information about files
219 declarations for routines that operate on/with those structures
244 data structures and routines, used to sumulate errors
[all …]
/illumos-gate/usr/src/man/man8/
H A Dsmbios.827 The SMBIOS image consists of a table of structures, each describing some aspect
30 option is specified, \fBsmbios\fR displays a summary of the structures that are
83 By default, \fBsmbios\fR elides output for structures whose type is marked as
103 Display only those structures whose type matches the specified integer type, as
126 Display raw hexadecimal data for the selected structures in addition to
130 human-readable output for the selected structures.
157 Successful completion. All structures in the SMBIOS image were examined
/illumos-gate/usr/src/man/man9f/
H A Dddi_soft_state.9f109 per-driver structures; everything else is managed by these routines.
115 such structures if required.
138 The space used by all the soft state structures allocated on a given state
146 structures in an MT-safe fashion, thus no additional locks should be necessary.
221 \fBExample 1 \fRCreating and Removing Data Structures
227 the driver's data structures.
336 If necessary, a hierarchy of state structures can be constructed by embedding
337 state pointers in higher order state structures.
/illumos-gate/usr/src/tools/smatch/src/Documentation/
H A Ddata-structures.txt2 - Describes most data structures used in sparse.
4 As far as the parsing structures go...
18 As with the various other structures, it has some common data and a union of sub-structures for the…
28 The linearized bytecode itself has a set of nested structures.
52 That covers most of the major data structures in Sparse.
/illumos-gate/usr/src/uts/common/sys/fibre-channel/fca/emlxs/
H A Demlxs_dump.h102 #define SID_MULT_ELEM 0x20 /* indicates structures, not bytes */
160 #define LEGEND_INTERNAL_MP "Driver-specific Internal Structures, Miniport"
161 #define LEGEND_INTERNAL_SP "Driver-specific Internal Structures, Storport"
162 #define LEGEND_INTERNAL_SOL "Driver-specific Internal Structures, Solaris"
163 #define LEGEND_INTERNAL_L7X "Driver-specific Internal Structures, Linux 7x"
164 #define LEGEND_INTERNAL_L8X "Driver-specific Internal Structures, Linux 8x"
165 #define LEGEND_SLI_STRUCTURES "SLI Interface Structures"
242 /* Sub-Legends associated with SLI Interface Structures */
250 #define LEGEND_DRIVER_SPEC "Driver-Specific Internal Structures"
332 /* This is a simplified form of the Dump Table Entry structures. */
/illumos-gate/usr/src/man/man3nsl/
H A Dt_alloc.3nsl74 transport function argument structures as specified below. This function will
96 where each of these structures may subsequently be used as an argument to one
100 Each of the above structures, except \fBT_INFO,\fR contains at least one field
116 \fBt_uderr\fR structures.
126 \fBt_uderr\fR structures.
136 structures.
176 Use of \fBt_alloc()\fR to allocate structures will help ensure the
H A Dxdr_complex.3nsl15 structures in a machine-independent fashion. Protocols such as remote procedure
17 routines are the \fBXDR\fR library routines for complex data structures. They
91 recursive data structures, such as binary trees or linked lists. If
104 \fBxdr_reference()\fR provides pointer chasing within structures. The
146 is a pointer to an array of \fBxdr_discrim\fR structures. Each structure
/illumos-gate/usr/src/man/man9/
H A DIntro.919 .Nd introduction to kernel concepts, device drivers, functions, and structures
65 structures, to device driver frameworks
79 Section 9S, structures, describes various structures that are filled out, their
93 9E and 9F discussions which often have more context for how these structures are
/illumos-gate/usr/src/man/man3socket/
H A Dsctp_getladdrs.3socket35 allocated array of \fBsockaddr_in\fR structures for an Internet Protocol (IPv4)
36 socket or an array of \fBsockaddr_in6\fR structures for an Internet Protocol
38 an IPv4 SCTP socket, the addresses returned in the \fBsockaddr_in\fR structures
40 \fBsockaddr_in6\fR structures can be IPv6 addresses or IPv4-mapped IPv6
H A Dsctp_getpaddrs.3socket35 dynamically allocated array of \fBsockaddr_in\fR structures for an Internet
36 Protocol (IPv4) socket or an array of \fBsockaddr_in6\fR structures for an
39 \fBsockaddr_in\fR structures are IPv4 addresses. For an IPv6 SCTP socket, the
40 addresses in the \fBsockaddr_in6\fR structures can be IPv6 addresses or
/illumos-gate/usr/src/man/man3xnet/
H A Dfreeaddrinfo.3xnet66 The \fBfreeaddrinfo()\fR function frees one or more \fBaddrinfo\fR structures
68 with those structures. If the \fBai_next\fR member of the structure is not
69 null, the entire list of structures is freed. The \fBfreeaddrinfo()\fR function
203 refers to a linked list of \fBaddrinfo\fR structures, each of which specifies a
225 structures are undefined.
228 All members in socket address structures returned by \fBgetaddrinfo()\fR that
231 structures.
/illumos-gate/usr/src/uts/i86xpv/os/
H A Dballoon.c60 * Various structures needed by the balloon thread
70 * For holding spare page_t structures - keep a singly-linked list.
198 * We want to add memory, but have no spare page_t structures. Use some of
199 * our new memory for the page_t structures.
220 * that will be required to hold page_t structures for all new pages. in balloon_init_new_pages()
227 * Given the number of page_t structures we need, is there also in balloon_init_new_pages()
245 * Figure out the number of page_t structures that can fit in metapgs in balloon_init_new_pages()
247 * This will cause us to initialize more page_t structures than we in balloon_init_new_pages()
259 * structures with invalid pagenums -- we deal with this situation in balloon_init_new_pages()
265 * Get a VA for the pages that will hold page_t and other structures. in balloon_init_new_pages()
[all …]
/illumos-gate/usr/src/man/man3ofmt/
H A Dofmt.3ofmt27 .Nd data structures and routines for printing output
72 library provides data structures and routines for printing output.
94 .Ss Data Structures
160 .Sx Data Structures ,
252 .Sx Data Structures .
/illumos-gate/usr/src/lib/libipmp/common/
H A Dipmp_query_impl.h33 * Private IPMP query interfaces and structures.
43 * List of ipmp_groupinfo_t structures.
51 * List of ipmp_ifinfo_t structures.
59 * List of ipmp_addrinfo_t structures.
/illumos-gate/usr/src/uts/common/sys/
H A Dfss.h77 /* list of fssproj structures */
84 uint32_t fssps_nproj; /* number of fssproj structures */
92 * One of these structures is allocated to each project running within each
138 * One of these structures is allocated to each zone running within
140 * than one cpu partition then it will have a few of these structures.
H A Dvfs_opreg.h41 * used in the the fs_operation_def structures.
54 * File systems use arrays of fs_operation_def structures to form
69 * structures. They contain all of the information necessary for the system
74 * (arrays of fs_operation_def structures). These routines use the master
/illumos-gate/usr/src/man/man3curses/
H A Dcurs_window.3curses120 Each \fBcurses\fR window maintains two data structures: the character image
126 updating. Since status structures are not shared, changes made to one window in
131 window to be reflected in the status structures of its ancestors. If
141 reflect the changes in the status structures of its ancestors. Applications
/illumos-gate/usr/src/cmd/sendmail/db/include/
H A Ddb_shash.h22 * field: the name of the field by which the "type" structures are linked.
52 * field: the name of the field by which the "type" structures are linked.
71 * field: the name of the field by which the "type" structures are linked.
94 * field: the name of the field by which the "type" structures are linked.
/illumos-gate/usr/src/uts/sun4u/lw8/sys/
H A Dsgfrutree.h109 * fru_get_children() fills an array of structures representing the
116 * On success, the number of node_t structures written is returned;
127 * fru_get_handles() fills an array of structures representing the
134 * On success, the number of fru_hdl_t structures written is returned;
/illumos-gate/usr/src/man/man3elf/
H A Delf_update.3elf34 only the \fBELF\fR descriptor's memory structures. Any modified structures are
71 When updating the internal structures, \fBelf_update()\fR sets some members
163 version of data structures written to the file. If the version is
/illumos-gate/usr/src/cmd/mdb/common/modules/nfs/
H A Dcommon.h35 * Generic hash table is an array of head structures starting at address
36 * array_addr. The number of the head structures in the array is array_len.
39 * linked list of member structures. The member structure type name is stored

12345678910>>...104