Query: ddi-no-autodetach
OS: opensolaris
Section: 9p
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
ddi-forceattach(9P) Kernel Properties for Drivers ddi-forceattach(9P)NAMEddi-forceattach, ddi-no-autodetach - properties controlling driver attach/detach behaviorDESCRIPTIONSolaris device drivers are attached by devfsadm(1M) and by the kernel in response to open(2) requests from applications. Drivers not cur- rently in use can be detached when the system experiences memory pressure. The ddi-forceattach and ddi-no-autodetach properties can be used to customize driver attach/detach behavior. The ddi-forceattach is an integer property, to be set globally by means of the driver.conf(4) file. Drivers with this property set to 1 are loaded and attached to all possible instances during system startup. The driver will not be auto-detached due to system memory pressure. The ddi-no-autodetach is an integer property to be set globally by means of the driver.conf(4) file or created dynamically by the driver on a per-instance basis with ddi_prop_update_int(9F). When this property is set to 1, the kernel will not auto-detach driver due to system memory pressure. Note that ddi-forceattach implies ddi-no-autodetach. Setting either property to a non-integer value or an integer value not equal to 1 pro- duces undefined results. These properties do not prevent driver detaching in response to reconfiguration requests, such as executing com- mands cfgadm(1M), modunload(1M), rem_drv(1M), and update_drv(1M).SEE ALSOdriver.conf(4) Writing Device Drivers SunOS 5.11 18 May 2001 ddi-forceattach(9P)
Related Man Pages |
---|
detach(9e) - v7 |
detach(9e) - suse |
detach(9e) - osf1 |
detach(9e) - bsd |
detach(9e) - redhat |
Similar Topics in the Unix Linux Community |
---|
error: field has incomplete type |
a reform in the intellectual property system |
My NIC driver didn't pass high pressure test! |