This section describes general kernel parameters relating to physical memory and stack size.
Number of usable pages of physical memory available on the system—not counting the memory where the core kernel and data are stored.
1 to amount of physical memory on system
Whenever you want to test the effect of running with less physical memory. Note that because this parameter does not take into account the memory used by the core kernel and data as well as various other data structures allocated early in the startup process, the value of physmem should be less than the actual number of pages that represent the smaller amount of memory.
8192 for all 32-bit SPARC and IA based platforms
16,384 for 64-bit sun4u platforms
0 to 262,144
Bytes in multiples of the value returned by getpagesize(3C).
Yes. Affects threads created after the variable is changed.
Must be greater than or equal to 8192 and less than or equal to 262,144 (256 x 1024) and must be a multiple of the system page size. If these conditions are not met, the following message is displayed:
Illegal stack size, Using N
The value of N is the default described above.
When the system panics because it has run out of stack space. The best solution for this problem is to determine why the system is running out of space and make a correction. Increasing the default stack size means that almost every kernel thread will have a larger stack, resulting in increased kernel memory consumption for no good reason, because that space will generally be unused. The increased consumption means that other resources competing for the same pool of memory will have the amount of space available to them reduced, possibly decreasing the system's ability to perform work. Among the side effects will be a reduction in the number of threads which the kernel can create. This solution should be treated as no more than an interim workaround until the root cause is remedied.
Maximum number of system events allowed to be queued waiting for delivery to the syseventd daemon. Once the size of the system event queue reaches this limit, no other system events will be allowed on the queue.
0 to MAXINT
The sysevent framework checks this value every time a system event is generated via ddi_log_sysevent(9) and sysevent_post_event(3).
When error log messages indicate that a system event failed to be logged, generated, or posted.
See logevent_max_q_sz for more information.