te
 Copyright (c) 2001, Sun Microsystems, Inc. All Rights Reserved.
 The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
 You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
 When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
 DDI-FORCEATTACH 9P "May 18, 2001"
 NAME
ddi-forceattach, ddi-no-autodetach - properties controlling driver
attach/detach behavior

 DESCRIPTION

Solaris device drivers are attached by devfsadm(8) and by the kernel in
response to open(2) requests from applications. Drivers not currently 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(5) 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(5) 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 produces
undefined results. These properties do not prevent driver detaching in response
to reconfiguration requests, such as executing commands cfgadm(8),
modunload(8), rem_drv(8), and update_drv(8).

 SEE ALSO

 driver.conf (5) 

Writing Device Drivers