From 990c81172582cac571c0c28ef76cf4e30412828a Mon Sep 17 00:00:00 2001 From: yuanchao Date: Wed, 27 Nov 2024 11:04:07 +0800 Subject: [PATCH] fix: modify the vhost_socket_path type --- server/agent_config/README-CH.md | 2 +- server/agent_config/README.md | 16 ++++++++-------- server/agent_config/template.yaml | 16 ++++++++-------- 3 files changed, 17 insertions(+), 17 deletions(-) diff --git a/server/agent_config/README-CH.md b/server/agent_config/README-CH.md index dcbf1837256..de6e03b0a4f 100644 --- a/server/agent_config/README-CH.md +++ b/server/agent_config/README-CH.md @@ -2811,7 +2811,7 @@ inputs: **模式**: | Key | Value | | ---- | ---------------------------- | -| Type | bool | +| Type | string | **详细描述**: diff --git a/server/agent_config/README.md b/server/agent_config/README.md index 7ef34145f76..550cf9ab564 100644 --- a/server/agent_config/README.md +++ b/server/agent_config/README.md @@ -2876,7 +2876,7 @@ inputs: **Schema**: | Key | Value | | ---- | ---------------------------- | -| Type | bool | +| Type | string | **Description**: @@ -3554,15 +3554,15 @@ You can use the command 'lspci -vmmk' to find the network card driver type. For Rev: 02 Driver: igb_uio Module: i40e - -In the example above, "Driver: igb_uio" indicates a DPDK-managed device (other options include -"vfio-pci" and "uio_pci_generic", which are also managed by DPDK). The actual driver is 'i40e' + +In the example above, "Driver: igb_uio" indicates a DPDK-managed device (other options include +"vfio-pci" and "uio_pci_generic", which are also managed by DPDK). The actual driver is 'i40e' (derived from 'Module: i40e'). -You can use the sustainable profiling feature provided by DeepFlow to perform function profiling on the DPDK application and check the specific interface names. Alternatively, you can run the `perf` command on the node where the agent is located: -`perf record -F97 -a -g -p -- sleep 30` -and then use -`perf script | grep -E 'recv|xmit'` +You can use the sustainable profiling feature provided by DeepFlow to perform function profiling on the DPDK application and check the specific interface names. Alternatively, you can run the `perf` command on the node where the agent is located: +`perf record -F97 -a -g -p -- sleep 30` +and then use +`perf script | grep -E 'recv|xmit'` to confirm the driver interfaces. Below are some common interface names for different drivers, for reference only: diff --git a/server/agent_config/template.yaml b/server/agent_config/template.yaml index 051c4984941..2a7efdbf062 100644 --- a/server/agent_config/template.yaml +++ b/server/agent_config/template.yaml @@ -1790,7 +1790,7 @@ inputs: # name: vHost User # description: vhost_user: - # type: bool + # type: string # name: vHost Socket Path # unit: # range: [] @@ -2228,16 +2228,16 @@ inputs: # Driver: igb_uio # Module: i40e # ``` - # In the example above, "Driver: igb_uio" indicates a DPDK-managed device (other options include - # "vfio-pci" and "uio_pci_generic", which are also managed by DPDK). The actual driver is 'i40e' + # In the example above, "Driver: igb_uio" indicates a DPDK-managed device (other options include + # "vfio-pci" and "uio_pci_generic", which are also managed by DPDK). The actual driver is 'i40e' # (derived from 'Module: i40e'). # # You can use the sustainable profiling feature provided by DeepFlow to perform function profiling # on the DPDK application and check the specific interface names. Alternatively, you can run the - # `perf` command on the node where the agent is located: - # `perf record -F97 -a -g -p -- sleep 30` - # and then use - # `perf script | grep -E 'recv|xmit'` + # `perf` command on the node where the agent is located: + # `perf record -F97 -a -g -p -- sleep 30` + # and then use + # `perf script | grep -E 'recv|xmit'` # to confirm the driver interfaces. # # Below are some common interface names for different drivers, for reference only: @@ -2294,7 +2294,7 @@ inputs: # # 可以使用 deepflow 提供的可持续剖析功能对 DPDK 应用做函数剖析查看具体接口名字，也可以使用 perf 命令 # 在agent所在节点上运行 `perf record -F97 -a -g -p -- sleep 30`，`perf script | grep -E 'recv|xmit'` - # 来确认驱动接口。 + # 来确认驱动接口。 # # 下面列出了不同驱动对应的接口名称，仅供参考: # 1. Physical NIC Drivers: