Lines Matching refs:that

14 configfs is a ram-based filesystem that provides the converse of
23 write(2).  The important point is that the object is created and
46 These are modules that register their item types with configfs as
70 Imagine there's a Network Block Device (NBD) driver that allows you to
72 for its configuration.  Obviously, there will be a nice program that
73 sysadmins use to configure FakeNBD, but somehow that program has to tell
105 object in the subsystem.  It has attributes that match values on that
106 object.  configfs handles the filesystem representation of that object
111 collection of items that share the same attributes and operations.
113 handles that.  The group has a set of operations to perform these tasks
142 structure that actually represents what the subsystem is doing.  The
143 config_item portion of that structure is how the object interacts with
157 among other things.  For that, it needs a type.
177 operations can be performed on a config_item.  All items that have been
199 If an attribute is readable and provides a ->show method, that method will
201 attribute is writable and provides a ->store  method, that method will be
224 that item means that a group can behave as an item in its own right.
254 The subsystem must config_item_put() the reference that was initialized
261 (assuming that it has no children to keep it busy).  The subsystem is
302 will be visible via configfs.  At that point, mkdir(2) can be called and
315 There is an extra bonus that configfs provides.  The config_groups and
316 config_items are arranged in a hierarchy due to the fact that they
332 yet been unlinked.  This means that an item's ci_parent pointer will
333 never be NULL while the item is in configfs, and that an item will only
386 Each group in that array is populated in the configfs tree at the same
390 also means every default group child associated with that parent group.
399 example, ocfs2 mounts depend on a heartbeat region item.  If that
405 configfs_depend_item() on an existing item to tell configfs that it is
406 depended on.  configfs will then return -EBUSY from rmdir(2) for that
413 be providing an API that external subsystems call.
428 default values can be specified for the item's attributes such that the
435 The simple example assumes that the subsystem merely waits until all the
439 that condition is met.
441 Far better would be an explicit action notifying the subsystem that the
444 initialized in a way that makes sense.  configfs provides this as
451 Any group that provides the ct_group_ops->commit_item() method has