Lines Matching refs:A
29 A configfs config_item is created via an explicit userspace operation:
98 A fakenbd connection can be created with mkdir(2). The name is
121 Every object in configfs is a config_item. A config_item reflects an
127 Items are created and destroyed inside a config_group. A group is a
132 A subsystem is the top level of a client module. During initialization,
134 appears as a directory at the top of the configfs filesystem. A
263 A config_item cannot live in a vacuum. The only way one can be created
298 A group creates child items by providing the
336 A config_group cannot be removed while it still has child items. This
344 A subsystem must register itself, usually at module_init time. This
355 A subsystem consists of a toplevel config_group and a mutex.
380 appear in a filesystem. A subsystem is NEVER to touch the filesystem
385 A subsystem can navigate the cg_children list and the ci_parent pointer
392 A subsystem will be prevented from acquiring the mutex while a newly
409 A config_item may provide the ct_item_ops->allow_link() and
417 allows linking to target item, it returns 0. A source item may wish to
426 A config_item cannot be removed while it links to any other item, nor
433 A new config_group may want to have two types of child config_items.
449 A configfs subsystem specifies default groups by adding them using the
470 configfs_undepend_item(). A client driver can call
477 they will conflict. They can block and allocate. A client driver