Lines Matching refs:storage
9 storage. It is only available with ``CONFIG_CGROUP_BPF``, and to programs that
11 storage is identified by the cgroup the program is attached to.
13 The map provide a local storage at the cgroup that the BPF program is attached
38 map will share the same storage. Otherwise, if the type is
42 To access the storage in a program, use ``bpf_get_local_storage``::
51 ``struct bpf_spin_lock`` to synchronize the storage. See
128 storage. The non-per-CPU will have the same memory region for each storage.
130 Prior to Linux 5.9, the lifetime of a storage is precisely per-attachment, and
133 multiple attach types, and each attach creates a fresh zeroed storage. The
134 storage is freed upon detach.
139 one storage map of each type. Because of map can only be used by one BPF
140 program, sharing of this cgroup's storage with other BPF programs were
143 Since Linux 5.9, storage can be shared by multiple programs. When a program is
144 attached to a cgroup, the kernel would create a new storage only if the map
146 the old storage is reused for the new attachment. If the map is attach type
149 will not directly free the storage, but it may cause the reference to the map
150 to reach zero and indirectly freeing all storage in the map.
160 APIs to read or update the storage for a given attachment. For Linux 5.9
165 The storage is bound at attach time. Even if the program is attached to parent
166 and triggers in child, the storage still belongs to the parent.
169 Program test runs always use a temporary storage.