Lines Matching refs:via

21 appear in sysfs, allowing userspace to read the attributes via
22 readdir(3)/read(2).  It may allow some attributes to be modified via
27 A configfs config_item is created via an explicit userspace operation:
28 mkdir(2).  It is destroyed via rmdir(2).  The attributes appear at
29 mkdir(2) time, and can be read or modified via read(2) and write(2).
51 An item is created via mkdir(2).  The item's attributes will also
65 item cannot be destroyed if any other item has a link to it (via
66 symlink(2)).  Links can be removed via unlink(2).
99 That's it.  That's all there is.  Now the device is configured, via the
151 All users of a config_item should have a reference on it via
152 config_item_get(), and drop the reference when they are done via
207 is via mkdir(2) on a config_group.  This will trigger creation of a
226 accomplished via the group operations specified on the group's
299 group via the usual group _init() functions, and it must also have
302 will be visible via configfs.  At that point, mkdir(2) can be called and
319 this reason, the hierarchy is mirrored via the config_group->cg_children
340 configfs provides a simple group via the group->item parent/child
342 outside of the parent/child connection.  This is implemented via
358 notified via the ->drop_link() method.  Like the ->drop_item() method,
392 As a consequence of this, default_groups cannot be removed directly via
416 it asks for a heartbeat region item.  This is done via a call into the
448 committed via rename(2).  The item is moved from a directory where it
464 shutdown, or "uncommitted".  Again, this is done via rename(2), this