| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-cdx | 8 also deleted from Linux.
|
| H A D | sysfs-fs-f2fs | 534 that when the compressed blocks are deleted, this count doesn't
542 that when the compressed blocks are deleted, this count doesn't
|
| /linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 500 do_something_gp() and find the newly deleted ``struct foo``.
|
| /linux/Documentation/RCU/ |
| H A D | RTFP.txt | 258 node was to be deleted, and waits until all such processes have
291 node was to be deleted, and waits until all such processes have
|
| H A D | listRCU.rst | 90 or deleted, rather than being modified in place. This is a rare example
229 deleted, without in-place modification, it is very easy to use RCU!
320 function in ipc/shm.c). This code checks a *deleted* flag under a
328 For the deleted-flag technique to be helpful, why is it necessary
346 if (e->deleted) {
375 e->deleted = 1;
386 Note that this example assumes that entries are only added and deleted.
492 If stale data cannot be tolerated, then a *deleted* flag may be used
494 function to reject newly deleted data.
499 For the deleted-flag technique to be helpful, why is it necessary
[all …]
|
| H A D | rcu.rst | 10 must be long enough that any readers accessing the item being deleted have
|
| H A D | rculist_nulls.rst | 101 and previous value of 'obj->key'. Otherwise, an item could be deleted
124 But thanks to SLAB_TYPESAFE_BY_RCU, beware a deleted object can be reused
|
| H A D | rcuref.rst | 51 has already been deleted from the list/array. Use atomic_inc_not_zero()
|
| H A D | whatisRCU.rst | 474 * to ensure that the structure does not get deleted out
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | Smack.rst | 212 If label is "-DELETE" a matched entry will be deleted.
|
| /linux/Documentation/admin-guide/ |
| H A D | binderfs.rst | 70 Binderfs binder devices can be deleted via `unlink() <unlink_>`_. This means
72 ``binder-control`` device cannot be deleted since this would make the binderfs
73 instance unusable. The ``binder-control`` device will be deleted when the
|
| H A D | cgroup-v2.rst | 291 is removed subsequently, " (deleted)" is appended to the path::
295 0::/test-cgroup/test-cgroup-nested (deleted)
967 dying after being deleted by a user. The cgroup will remain
|
| H A D | module-signing.rst | 132 it can be deleted or stored securely. The public key gets built into the
|
| H A D | spkguide.txt | 969 find that all the mappings you didn't include in your file got deleted
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | devices.rst | 89 anymore, they'll be deleted.
|
| H A D | hugetlb.rst | 121 This is usually when the HugeTLB file is deleted, and not when the task that
|
| H A D | rdma.rst | 57 deleted after processes migrated. This allow progress migration as well with
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | vdo-design.rst | 131 not been deleted from its chapter. Like the chapter index, the volume index
|
| H A D | writecache.rst | 110 6. the cache device is now inactive and it can be deleted
|
| /linux/Documentation/arch/powerpc/ |
| H A D | kvm-nested.rst | 347 deleted. No specific vCPU delete call is provided.
|
| /linux/Documentation/arch/s390/ |
| H A D | driver-model.rst | 196 return code 0, the device will be deleted as usual (also when no
|
| /linux/Documentation/arch/x86/ |
| H A D | boot.rst | 1214 They should normally not be deleted from the kernel command line even
|
| /linux/Documentation/bpf/ |
| H A D | map_cpumap.rst | 49 CPUMAP entries can only be updated/looked up/deleted from user space and not
93 CPU entries can be deleted using the ``bpf_map_delete_elem()``
|
| H A D | map_devmap.rst | 74 DEVMAP entries can only be updated/deleted from user space and not
132 Net device entries can be deleted using the ``bpf_map_delete_elem()``
|
| H A D | map_hash.rst | 87 Hash entries can be deleted using the ``bpf_map_delete_elem()``
136 Note that if ``cur_key`` gets deleted then ``bpf_map_get_next_key()``
|