| /linux-6.6.21/net/sched/ |
| D | sch_ingress.c | 83 bool created; in ingress_init() local
91 entry = tcx_entry_fetch_or_create(dev, true, &created); in ingress_init()
96 if (created) in ingress_init()
247 bool created; in clsact_init() local
256 entry = tcx_entry_fetch_or_create(dev, true, &created); in clsact_init()
261 if (created) in clsact_init()
275 entry = tcx_entry_fetch_or_create(dev, false, &created); in clsact_init()
280 if (created) in clsact_init()
|
| /linux-6.6.21/Documentation/PCI/endpoint/ |
| D | pci-endpoint-cfs.rst | 39 entries corresponding to EPF driver will be created by the EPF core.
56 (These entries are created by the framework when any new <EPF Device> is
57 created)
86 be created by the user to represent the virtual functions that are bound to
95 entries corresponding to EPC device will be created by the EPC core.
109 <EPF Device>. These symbolic links should be created by the user to
116 all the EPF devices are created and linked with the EPC device.
|
| /linux-6.6.21/Documentation/ABI/testing/ |
| D | sysfs-bus-vfio-mdev | 9 Each supported type is a directory whose name is created
41 devices sysfs entries which are created of this <type-id>.
48 devices of type <type-id> that can be created. This is a
53 the number of available instances could be created before
69 mediated device that will get created of type <type-id>.
81 mediated device that will get created of type <type-id>.
102 directory of which this mediated device is created.
|
| D | sysfs-class-vduse | 15 This directory entry is created for the control device
23 This directory entry is created when a VDUSE device is
24 created via the control device.
|
| D | sysfs-bus-event_source-devices-hv_gpci | 92 * This sysfs file will be created only for power10 and above platforms.
96 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
124 * This sysfs file will be created only for power10 and above platforms.
128 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
156 * This sysfs file will be created only for power10 and above platforms.
160 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
188 * This sysfs file will be created only for power10 and above platforms.
192 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
220 * This sysfs file will be created only for power10 and above platforms.
224 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
|
| D | configfs-rdma_cm | 12 for this HCA has to be created:
28 will be created with this TOS as default.
|
| D | sysfs-class-rtrs-server | 6 directory entry with the name of that session is created in here.
12 Description: When new path is created by writing to "add_path" entry on client side,
13 a directory entry named as <source address>@<destination address> is created
|
| /linux-6.6.21/Documentation/userspace-api/media/dvb/ |
| D | net-add-if.rst | 36 ULE) and the interface number for the new interface to be created. When
38 created.
41 filled with the number of the created interface.
|
| D | net-get-if.rst | 13 NET_GET_IF - Read the configuration data of an interface created via - :ref:`NET_ADD_IF <net>`.
38 created yet with :ref:`NET_ADD_IF <net>`, it will return -1 and fill
|
| /linux-6.6.21/net/ceph/ |
| D | crypto.c | 79 if (*p + sizeof(u16) + sizeof(key->created) + in ceph_crypto_key_encode()
83 ceph_encode_copy(p, &key->created, sizeof(key->created)); in ceph_crypto_key_encode()
93 ceph_decode_need(p, end, 2*sizeof(u16) + sizeof(key->created), bad); in ceph_crypto_key_decode()
95 ceph_decode_copy(p, &key->created, sizeof(key->created)); in ceph_crypto_key_decode()
|
| /linux-6.6.21/Documentation/leds/ |
| D | uleds.rst | 12 When the driver is loaded, a character device is created at /dev/uleds. To
22 A new LED class device will be created with the name given. The name can be
34 Multiple LED class devices are created by opening additional file handles to
|
| /linux-6.6.21/kernel/bpf/ |
| D | tcx.c | 12 bool created, ingress = attr->attach_type == BPF_TCX_INGRESS; in tcx_prog_attach() local
34 entry = tcx_entry_fetch_or_create(dev, ingress, &created); in tcx_prog_attach()
49 } else if (created) { in tcx_prog_attach()
145 bool created, ingress = tcx->location == BPF_TCX_INGRESS; in tcx_link_prog_attach() local
151 entry = tcx_entry_fetch_or_create(dev, ingress, &created); in tcx_link_prog_attach()
163 } else if (created) { in tcx_link_prog_attach()
|
| /linux-6.6.21/Documentation/driver-api/driver-model/ |
| D | binding.rst | 63 A symlink is created in the bus's 'devices' directory that points to
66 A symlink is created in the driver's 'devices' directory that points
69 A directory for the device is created in the class's directory. A
70 symlink is created in that directory that points to the device's
73 A symlink can be created (though this isn't done yet) in the device's
75 top-level directory. One can also be created to point to its driver's
|
| /linux-6.6.21/Documentation/filesystems/ |
| D | efivarfs.rst | 7 The efivarfs filesystem was created to address the shortcomings of
14 Variables can be created, deleted and modified with the efivarfs
23 files that are not well-known standardized variables are created
|
| /linux-6.6.21/include/net/ |
| D | tcx.h | 100 tcx_entry_fetch_or_create(struct net_device *dev, bool ingress, bool *created) in tcx_entry_fetch_or_create() argument
104 *created = false; in tcx_entry_fetch_or_create()
109 *created = true; in tcx_entry_fetch_or_create()
|
| /linux-6.6.21/arch/arm/boot/dts/aspeed/ |
| D | facebook-bmc-flash-layout.dtsi | 34 * Although the master partition can be created by enabling
36 * explicitly created to avoid breaking legacy applications.
|
| D | facebook-bmc-flash-layout-128.dtsi | 52 * Although the master partition can be created by enabling
54 * explicitly created to avoid breaking legacy applications.
|
| /linux-6.6.21/arch/x86/kvm/mmu/ |
| D | mmutrace.h | 159 TP_PROTO(struct kvm_mmu_page *sp, bool created),
160 TP_ARGS(sp, created),
164 __field(bool, created)
169 __entry->created = created;
173 __entry->created ? "new" : "existing")
|
| /linux-6.6.21/Documentation/driver-api/ |
| D | vfio-mediated-device.rst | 93 * @probe: called when new device created
127 used to trigger the creation of a mdev_device. The created mdev_device will be
134 Which will unbind and destroy all the created mdevs and remove the sysfs files.
192 The [<type-id>] name is created by adding the device driver string as a prefix
200 This attribute shows which device API is being created, for example,
206 created.
211 created.
246 Mediated devices can be created and assigned at runtime. The procedure to hot
|
| /linux-6.6.21/drivers/infiniband/ulp/ipoib/ |
| D | ipoib_fs.c | 102 unsigned long created; in ipoib_mcg_seq_show() local
108 ipoib_mcast_iter_read(iter, &mgid, &created, &queuelen, in ipoib_mcg_seq_show()
120 gid_buf, created, queuelen, in ipoib_mcg_seq_show()
|
| /linux-6.6.21/Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 36 as well as the major and minor numbers of the character device that was created.
38 example ``/dev/tpm10`` was created, the number (``dev_num``) 10 is returned.
40 Once the device has been created, the driver will immediately try to talk
|
| /linux-6.6.21/Documentation/usb/ |
| D | gadget_configfs.rst | 62 For each gadget to be created its corresponding directory must be created::
82 In order to have a place to store them, a strings subdirectory must be created
93 Further custom string descriptors can be created as directories within the
107 directories must be created:
120 Each configuration also needs its strings, so a subdirectory must be created
137 directory must be created::
158 At this moment a number of gadgets is created, each of which has a number of
364 a number of its default sub-groups created automatically.
|
| /linux-6.6.21/Documentation/admin-guide/sysctl/ |
| D | user.rst | 25 the user in the user namespace who created the object and
29 who created user namespaces the creation of the object happens
33 This recursive counting of created objects ensures that creating a
|
| /linux-6.6.21/Documentation/networking/devlink/ |
| D | devlink-port.rst | 115 before a bus specific device for the function is created. However, when
116 SRIOV is enabled, virtual function devices are created on the PCI bus.
143 device created for the PCI VF/SF.
302 it is deployed. Subfunction is created and deployed in unit of 1. Unlike
317 A subfunction is created using a devlink port interface. A user adds the
326 A subfunction devlink port is created but it is not active yet. That means the
327 entities are created on devlink side, the e-switch port representor is created,
328 but the subfunction device itself is not created. A user might use e-switch port
338 A subfunction device is created on the :ref:`Documentation/driver-api/auxiliary_bus.rst <auxiliary_…
348 Represents a single devlink port; created/destroyed by the driver. Since leaf
[all …]
|
| /linux-6.6.21/tools/perf/Documentation/ |
| D | intel-hybrid.txt | 14 The 'cpus' files are created under the directories. For example,
52 two events are created automatically. One is for atom, the other is for
85 are created automatically.
137 As previous, two events are created.
179 besides of software events, following events are created and
|