Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix some typo errors of some documents #345

Merged
merged 1 commit into from
May 21, 2024
Merged

Fix some typo errors of some documents #345

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/kmesh_development_guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -302,7 +302,7 @@ Kmesh主要功能模块分为：

![inet_ops_replace](pics/design/inet_ops_replace.png)

延迟建联逻辑：
延迟建链逻辑：

![defer-conn](pics/design/defer-conn.png)

Expand Down
4 changes: 2 additions & 2 deletions docs/multiple dataplane_CN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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框架替换。

## 修改后默认行为对外变更

Expand Down
4 changes: 2 additions & 2 deletions docs/multiple dataplane_EN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading