On Thu, Jul 21, 2022 at 09:56:05AM +0800, Slark Xiao wrote: > diff --git a/Documentation/bpf/map_cgroup_storage.rst b/Documentation/bpf/map_cgroup_storage.rst > index cab9543017bf..8e5fe532c07e 100644 > --- a/Documentation/bpf/map_cgroup_storage.rst > +++ b/Documentation/bpf/map_cgroup_storage.rst > @@ -31,7 +31,7 @@ The map uses key of type of either ``__u64 cgroup_inode_id`` or > }; > > ``cgroup_inode_id`` is the inode id of the cgroup directory. > -``attach_type`` is the the program's attach type. > +``attach_type`` is the program's attach type. > > Linux 5.9 added support for type ``__u64 cgroup_inode_id`` as the key type. > When this key type is used, then all attach types of the particular cgroup and > @@ -155,7 +155,7 @@ However, the BPF program can still only associate with one map of each type > ``BPF_MAP_TYPE_CGROUP_STORAGE`` or more than one > ``BPF_MAP_TYPE_PERCPU_CGROUP_STORAGE``. > > -In all versions, userspace may use the the attach parameters of cgroup and > +In all versions, userspace may use the attach parameters of cgroup and > attach type pair in ``struct bpf_cgroup_storage_key`` as the key to the BPF map > APIs to read or update the storage for a given attachment. For Linux 5.9 > attach type shared storages, only the first value in the struct, cgroup inode For the bpf changes, Acked-by: Martin KaFai Lau <kafai@xxxxxx> -- Linux-cachefs mailing list Linux-cachefs@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/linux-cachefs
