- User Since
- Apr 26 2018, 6:21 PM (38 w, 3 d)
Sun, Jan 13
This is effectively what we did in SmartOS/illumos to address the issue:
Tue, Jan 8
Mon, Jan 7
Up until now, those structs have been kept opaque to the rest of the system, with accessor functions to perform necessary tasks/queries against them. Could you go into more detail about how your plans for dynamic VM_MAXCPU are impeded by similar constraints?