/linux/tools/net/ynl/samples/ |
H A D | rt-link.c | 66 /* rtnetlink doesn't provide info about the created object. in rt_link_create_netkit() 81 goto created; in rt_link_create_netkit() 87 created: in rt_link_create_netkit() 96 "Warning: interface created but received no notification, won't delete the interface\n"); in rt_link_create_netkit() 140 int created = 0; in main() local 150 created = rt_link_create_netkit(ys); in main() 151 if (created < 0) in main() 170 if (created) in main() 171 rt_link_del(ys, created); in main() 179 if (created) in main() [all...] |
/linux/Documentation/driver-api/cxl/linux/ |
H A D | overview.rst | 29 * Soft-Reserved IO Resource created for CFMWS entry 33 * Nodes created from ACPI CEDT CFMWS and SRAT Proximity domains (PXM) 37 * A default memory_tier is created with all nodes. 53 * root, port, and memdev devices created 58 * root, switch, and endpoint decoders created 62 * memory_region and endpoint devices created 74 * dax_region created 76 * DAX device created via DAX driver
|
/linux/net/sched/ |
H A 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() 248 bool created; in clsact_init() local 257 entry = tcx_entry_fetch_or_create(dev, true, &created); in clsact_init() 262 if (created) in clsact_init() 276 entry = tcx_entry_fetch_or_create(dev, false, &created); in clsact_init() 281 if (created) in clsact_init()
|
/linux/Documentation/PCI/endpoint/ |
H A 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/Documentation/ABI/testing/ |
H A 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.
|
H A 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.
|
H A 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, onl [all...] |
/linux/Documentation/infiniband/ |
H A D | ucaps.rst | 42 is created during the first call and subsequent calls increment the 45 The UCAP character device is created under /dev/infiniband, and its 62 is created when the first UCAP character device is created. 64 The UCAP character device is created under /dev/infiniband.
|
/linux/Documentation/userspace-api/media/dvb/ |
H A 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.
|
/linux/Documentation/leds/ |
H A 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/kernel/bpf/ |
H A 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 = link->attach_type == 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/Documentation/driver-api/driver-model/ |
H A 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/Documentation/filesystems/ |
H A 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/include/net/ |
H A D | tcx.h | 95 tcx_entry_fetch_or_create(struct net_device *dev, bool ingress, bool *created) in tcx_entry_fetch_or_create() argument 99 *created = false; in tcx_entry_fetch_or_create() 104 *created = true; in tcx_entry_fetch_or_create()
|
/linux/arch/arm/boot/dts/aspeed/ |
H A D | facebook-bmc-flash-layout.dtsi | 34 * Although the master partition can be created by enabling 36 * explicitly created to avoid breaking legacy applications.
|
H A 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/arch/x86/kvm/mmu/ |
H A D | mmutrace.h | 160 TP_PROTO(struct kvm_mmu_page *sp, bool created), 161 TP_ARGS(sp, created), 165 __field(bool, created) 170 __entry->created = created; 174 __entry->created ? "new" : "existing")
|
/linux/Documentation/driver-api/ |
H A 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/drivers/infiniband/ulp/ipoib/ |
H A 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() 115 " created: %10ld\n" in ipoib_mcg_seq_show() 120 gid_buf, created, queuelen, in ipoib_mcg_seq_show()
|
/linux/Documentation/userspace-api/ |
H A D | iommufd.rst | 24 small letter (iommufd) refers to the file descriptors created via /dev/iommu for 61 feature.) As such, it must be created with a given nesting parent stage-2 69 to those events. A FAULT object must be created first to get a fault_id that 87 must be created given a nesting parent HWPT_PAGING object, and then it would 97 vIOMMU objects created for individual slices of different physical IOMMUs. 123 vIOMMU object must be created first to get its viommu_id, which could be then 198 1. IOMMUFD_OBJ_IOAS is created via the IOMMU_IOAS_ALLOC uAPI. An iommufd can 203 2. IOMMUFD_OBJ_DEVICE is created when an external driver calls the IOMMUFD kAPI 210 3. IOMMUFD_OBJ_HWPT_PAGING can be created in two ways: 212 * IOMMUFD_OBJ_HWPT_PAGING is automatically created whe [all...] |
/linux/tools/testing/selftests/net/packetdrill/ |
H A D | tcp_eor_no-coalesce-small.pkt | 3 // skb created for the chunk. 26 // This chunk should not be appended to the skbs created for the previous chunk.
|
H A D | tcp_eor_no-coalesce-large.pkt | 3 // skb created for the chunk. The large chunk itself should be packetized as 27 // Write a 2KB chunk. This chunk should not be appended to the packets created
|
/linux/Documentation/security/tpm/ |
H A 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/Documentation/admin-guide/blockdev/ |
H A D | zoned_loop.rst | 24 number of conventional zones can be created. The storage for each zone of the 33 zone size. With this, the maximum capacity of a zloop zoned block device created 111 the zoned device will not be created. 126 For the device created (/dev/zloop0), the zone backing files are all created 143 The zoned device created (/dev/zloop0) can then be used normally:: 166 the device was first created. To fully delete a zoned device, its backing files
|
/linux/Documentation/usb/ |
H A 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.
|