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.
183 operations can be performed on a config_item.  All items that have been
186 reaches zero.  Items that wish to display an attribute need to provide
206 ct_item_ops->show_attribute() method, that method will be called
230 that item means that a group can behave as an item in its own right.
260 The subsystem must config_item_put() the reference that was initialized
267 (assuming that it has no children to keep it busy).  The subsystem is
308 will be visible via configfs.  At that point, mkdir(2) can be called and
331 There is an extra bonus that configfs provides.  The config_groups and
332 config_items are arranged in a hierarchy due to the fact that they
348 yet been unlinked.  This means that an item's ci_parent pointer will
349 never be NULL while the item is in configfs, and that an item will only
402 Each group in that array is populated in the configfs tree at the same
406 also means every default group child associated with that parent group.
415 example, ocfs2 mounts depend on a heartbeat region item.  If that
421 configfs_depend_item() on an existing item to tell configfs that it is
422 depended on.  configfs will then return -EBUSY from rmdir(2) for that
429 be providing an API that external subsystems call.
444 default values can be specified for the item's attributes such that the
451 The simple example assumes that the subsystem merely waits until all the
455 that condition is met.
457 Far better would be an explicit action notifying the subsystem that the
460 initialized in a way that makes sense.  configfs provides this as
467 Any group that provides the ct_group_ops->commit_item() method has