Lines Matching refs:can
29 mkdir(2) time, and can be read or modified via read(2) and write(2).
31 symlink(2) can be used to group items together. Unlike sysfs, the
35 Both sysfs and configfs can and should exist together on the same
40 configfs can be compiled as a module or into the kernel. You can access
52 appear at this time. readdir(3) can determine what the attributes are,
53 read(2) can query their default values, and write(2) can store new
66 symlink(2)). Links can be removed via unlink(2).
82 A fakenbd connection can be created with mkdir(2). The name is
118 subsystem is also a config_group, and can do everything a config_group
119 can.
177 operations can be performed on a config_item. All items that have been
206 A config_item cannot live in a vacuum. The only way one can be created
224 that item means that a group can behave as an item in its own right.
225 However, it can do more: it can create child items or groups. This is
270 teardown happens, the subsystem can implement the
302 will be visible via configfs. At that point, mkdir(2) can be called and
322 A subsystem can navigate the cg_children list and the ci_parent pointer
323 to see the tree created by the subsystem. This can race with configfs'
363 can it be removed while an item links to it. Dangling symlinks are not
376 "parent/subgroupN". Items of type 1 can now be created in
377 "parent/subgroup1", and items of type N can be created in
382 other child groups can be created on the parent group directly.
404 configfs_undepend_item(). A client driver can call
411 they will conflict. They can block and allocate. A client driver
420 If it fails, it was being torn down anyway, and heartbeat can gracefully
428 default values can be specified for the item's attributes such that the
429 item can do its work. Userspace must configure one or more attributes,
430 after which the subsystem can start whatever entity this item
449 can be modified to a directory where it cannot.
457 created in the "pending" directory. Its attributes can be modified at