From d162516ab0a2bc0414069e5e136270b301d9f16f Mon Sep 17 00:00:00 2001 From: "923048992@qq.com" <923048992@qq.com> Date: Tue, 21 May 2024 11:10:29 +0800 Subject: [PATCH] fix: typo Signed-off-by: 923048992@qq.com <923048992@qq.com> --- docs/kmesh_development_guide.md | 4 ++-- docs/multiple dataplane_CN.md | 4 ++-- docs/multiple dataplane_EN.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/kmesh_development_guide.md b/docs/kmesh_development_guide.md index 19c164272..33645e30f 100644 --- a/docs/kmesh_development_guide.md +++ b/docs/kmesh_development_guide.md @@ -157,7 +157,7 @@ Kmesh总体逻辑视图： ├── kernel # kmesh-runtime相关模块 │   ├── ko │   ├── ko_src # kmesh.ko -│   └── patches # 内核增强特性：延迟建联、bpf hook、bpf-helper等 +│   └── patches # 内核增强特性：延迟建链、bpf hook、bpf-helper等 ├── kmesh.spec ├── LICENSE ├── Makefile @@ -302,7 +302,7 @@ Kmesh主要功能模块分为： ![inet_ops_replace](pics/design/inet_ops_replace.png) - 延迟建联逻辑： + 延迟建链逻辑： ![defer-conn](pics/design/defer-conn.png) diff --git a/docs/multiple dataplane_CN.md b/docs/multiple dataplane_CN.md index 45178b1d7..513941d22 100644 --- a/docs/multiple dataplane_CN.md +++ b/docs/multiple dataplane_CN.md @@ -188,9 +188,9 @@ cni用于在集群创建新的Pod时，判断该Pod是否属于打上Kmesh标签 iptables -t nat -I 1 OUTPUT -j RETURN -#### ebpf cgroup/connectv4 +#### ebpf cgroup/connect4 -connectv4，获取当前进程的classid，如果为0x1000，则Kmesh ebpf进行纳管，走后续的4层转发或ULP框架替换。 +connect4，获取当前进程的classid，如果为0x1000，则Kmesh ebpf进行纳管，走后续的4层转发或ULP框架替换。 ## 修改后默认行为对外变更 diff --git a/docs/multiple dataplane_EN.md b/docs/multiple dataplane_EN.md index 0e90ea668..0fa7e6590 100644 --- a/docs/multiple dataplane_EN.md +++ b/docs/multiple dataplane_EN.md @@ -189,9 +189,9 @@ All packets on the contract path are short-circuited to Envoy: iptables -t nat -I 1 OUTPUT -j RETURN -#### ebpf PID group/connectv4 +#### ebpf PID cgroup/connect4 -connectv4, get the classid of the current process. If it is 0x1000, Kmesh ebpf will be used for management, and the subsequent 4-layer forwarding or ULP framework replacement will be used. +connect4, get the classid of the current process. If it is 0x1000, Kmesh ebpf will be used for management, and the subsequent 4-layer forwarding or ULP framework replacement will be used. ## Default behavior after modification