Lines Matching +full:user +full:- +full:defined

43 built-in limitations on certain data structures.
50 configuration-dependent rules and values to be maintained.
55 MAXUSERS refers to the value defined in the configuration file
63 It is referred to in other calculations as NPROC and is defined to be
72 It is defined as
82 It is defined as
92 result of a \fIfork\fP.  This is defined to be
102 This is defined as
108 The number of ``c-list'' structures.  C-list structures are
110 Their number is defined as
117 This is defined as 256 (a quarter megabyte of memory) in /sys/h/mbuf.h.
125 quota structure is kept per user.  This is defined to be
133 One dquot structure is required per user, per active file system quota.
134 That is, when a user manipulates a file on a file system on which
135 quotas are enabled, the information regarding the user's quotas on
136 that file system must be in-core.  This information is cached, so
137 that not all information must be present in-core all the time.
138 This is defined as
147 This is defined to be
159 Run-time calculations
161 The most important data structures sized at run-time are those used in
186 or the default may be overridden with a configuration-file option.
205 As distributed, the sum of the virtual sizes of the core-resident
213 Other per-process limits discussed here may be changed with similar options
215 Soft, user-changeable limits are set to 512K bytes for stack (DFLSSIZ)
235 for system page tables mapping user page tables
237 That is, the sum of the virtual memory sizes of all (completely- or partially-)
243 Each page of system page tables allows 8 megabytes of user virtual memory.
259 It may be increased arbitrarily, with the caveat that the user structure
264 by the size of the index fields in the core-map (/sys/h/cmap.h).