Lines Matching full:subsystem

50 subsystems.  Once a client subsystem is loaded, it will appear as a
122 object in the subsystem.  It has attributes that match values on that
124 and its attributes, allowing the subsystem to ignore all but the
132 A subsystem is the top level of a client module.  During initialization,
133 the client module registers the subsystem with configfs, the subsystem
135 subsystem is also a config_group, and can do everything a config_group
162 structure that actually represents what the subsystem is doing.  The
176 Usually a subsystem wants the item to display and/or store attributes,
300 mkdir(2) in the group's directory.  The subsystem allocates a new
305 If the subsystem wants the child to be a group itself, the subsystem
312 The subsystem must config_item_put() the reference that was initialized
313 upon item allocation.  If a subsystem has no work to do, it may omit
315 config_item_put() on the item on behalf of the subsystem.
320    (assuming that it has no children to keep it busy).  The subsystem is
321    responsible for responding to this.  If the subsystem has references to
323    for the item to actually disappear from the subsystem's usage.  But it
329 teardown happens, the subsystem can implement the
344 A subsystem must register itself, usually at module_init time.  This
345 tells configfs to make the subsystem appear in the file tree::
355 A subsystem consists of a toplevel config_group and a mutex.
356 The group is where child config_items are created.  For a subsystem,
358 configfs_register_subsystem(), the subsystem must have initialized the
362 When the register call returns, the subsystem is live, and it
364 the subsystem must be ready for it.
370 subsystem/group and the simple_child item in
375 Hierarchy Navigation and the Subsystem Mutex
380 appear in a filesystem.  A subsystem is NEVER to touch the filesystem
381 parts, but the subsystem might be interested in this hierarchy.  For
385 A subsystem can navigate the cg_children list and the ci_parent pointer
386 to see the tree created by the subsystem.  This can race with configfs'
387 management of the hierarchy, so configfs uses the subsystem mutex to
388 protect modifications.  Whenever a subsystem wants to navigate the
389 hierarchy, it must do so under the protection of the subsystem
392 A subsystem will be prevented from acquiring the mutex while a newly
398 a subsystem to trust ci_parent and cg_children while they hold the
419 in its own subsystem).
423 this is a void function and cannot return failure.  The subsystem is
449 A configfs subsystem specifies default groups by adding them using the
454 method call notifies the subsystem the parent group is going away, it