RoCE QoS configuration - Priority mapping

已于 2022-02-15 22:10:22 修改
阅读量3k 收藏 10
点赞数 2
分类专栏： RoCE QoS 文章标签： 网络
于 2019-12-23 11:31:04 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/sunshuying1010/article/details/103661289
版权

RoCE QoS configuration - Priority mapping


考虑了很久，为了表达准确一些，还是决定用英文来写。

1. Priority configuration for RoCE

Both VPI verbs and RDMA_CM provide API for RoCE QoS configuration. With mlnx_ofed installed on the system, application can use multiple methods to set priority on RoCE traffic. Details are provided in this section.

1.1. Trust L2 - PCP based QoS

PCP based QoS can be configured for RoCEv1 and RoCEv2 traffic.

1.1.1. With VPI verbs

QPs can be created with specific SL (Service Level, 4 bits, range 0-15) from application, i.e.:

struct ibv_qp_attr *attr;
attr->qp_state = IBV_QPS_RTR;
attr->ah_attr.sl = xxx;
ibv_modify_qp(qp, attr, flags);

Device driver maps SL to PCP field (3 bits) - PCP takes 3 LSB’s of SL, it stands for UP (User Priority), UP is used in VLAN header:

UP = SL & 0x7

UP would be mapped to HW Traffic Class, the mapping from UP to TC can be checked and modified by “mlnx_qos” with option “–prio_tc=LIST”.

The mapping from SL to TC in mode of PCP based QoS:

Service LevelUser PriorityHW Traffic Class
0, 80default 0, configurable with “mlnx_qos --prio_tc”
1, 91default 1, configurable with “mlnx_qos --prio_tc”
2, 102default 2, configurable with “mlnx_qos --prio_tc”
3, 113default 3, configurable with “mlnx_qos --prio_tc”
4, 124default 4, configurable with “mlnx_qos --prio_tc”
5, 135default 5, configurable with “mlnx_qos --prio_tc”
6, 146default 6, configurable with “mlnx_qos --prio_tc”
7, 157default 7, configurable with “mlnx_qos --prio_tc”

“ib_write_bw -S ” can be used to check whether RoCE traffic is transmitted via expected priority.

1.1.2. With RDMA_CM

ToS can be configured on RDMA_CM QPs via API rdma_set_option(), with option RDMA_OPTION_ID_TOS;
Linux command line “cma_roce_tos” can be used to set default ToS.

In kernel, ToS {0, 8, 24, 16} would be mapped to SKB Priority {0, 2, 4, 6}, reference kernel code is in include/net/route.h::rt_tos2priority(u8 tos)

Device driver maps SKB Priority to User Priority, the mapping is defined by user, “ip link set dev [vlan interface] type vlan egress-qos-map [sk_prio2egress_prio mapping]” can be used in Linux command line to set the mapping.

UP would be mapped to HW Traffic Class, “mlnx_qos -i [interface] --prio_tc=LIST” is for user setting.

The mapping from ToS to TC in mode of PCP based QoS:

Type of ServiceSKB PriorityUser PriorityHW Traffic Class
0…7, 32…39, 64…71, 96…103, 128…135, 160…167, 192…199, 224…2310Need user to config with “egress-qos-map”Configurable with “mlnx_qos --prio_tc”
8…15, 40…47, 72…79, 104…111, 136…143, 168…175, 200…207, 232…2392Need user to config with “egress-qos-map”Configurable with “mlnx_qos --prio_tc”
16…23, 48…55, 80…87, 112…119, 144…151, 176…183, 208…215, 240…2474Need user to config with “egress-qos-map”Configurable with “mlnx_qos --prio_tc”
24…31, 56…63, 88…95, 120…127, 152…159, 184…191, 216…223, 248…2556Need user to config with “egress-qos-map”Configurable with “mlnx_qos --prio_tc”

“ib_write_bw -R --tos [ToS value]” can be used to check whether RoCE traffic is transmitted via expected priority.

1.2. Trust L3 - DSCP based QoS

DSCP based QoS can be configured for RoCEv2 traffic, it is not applicable for RoCEv1.

1.2.1. With VPI Verbs

QPs can be created with specific TClass (Traffic Class, 8 bits, range 0-255) from application.
Device driver maps TClass to DSCP field (6 bits) in IP header. DSCP takes 6 MSB’s of Tclass:

DSCP = TClass >> 2

Device driver maps DSCP to User Priority, the mapping can be configured by user with Linux command line “mlnx_qos -i --dscp2prio=DSCP2PRIO”.

UP would be mapped to HW Traffic Class, “mlnx_qos -i [interface] --prio_tc=LIST” is for user to configure the mapping.

The mapping from TClass to TC in mode of DSCP based QoS:

TClassDSCPUser PriorityHW Traffic Class
0…310…7Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
32…638…15Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
64…9516…23Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
96…12724…31Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qo --prio_tcs”
128…15932…39Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
160…19140…47Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
192…22348…55Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
224…25556…63Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”

“ib_write_bw --tclass [TClass value]” can be used to check whether RoCE traffic is transmitted via expected priority.

1.2.2. With RDMA_CM

In this mode, ToS (Type of Service) has range 0-255, and is regarded by device driver as the value of TClass.
ToS can be configured on RDMA_CM QPs via API rdma_set_option(), with option RDMA_OPTION_ID_TOS;
Linux command line “cma_roce_tos” can be used to set default ToS.
The mappings of “ToS(TClass) – DSCP – User Priority – HW Traffic Class” are the same as described in VPI verbs method in mode of DSCP based QoS configuration:

ToSDSCPUser PriorityHW Traffic Class
0…310…7Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
32…638…15Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
64…9516…23Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
96…12724…31Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
128…15932…39Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
160…19140…47Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
192…22348…55Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”
224…25556…63Configurable with “mlnx_qos --dscp2prio”Configurable with “mlnx_qos --prio_tc”

“ib_write_bw -R --tos [ToS value]” can be used to check whether RoCE traffic is transmitted via expected priority.

1.3. Summary

The table is a summary for priority configuration on RoCE traffic as described upon, including:

  • traffic type - RoCEv1 and RoCEv2
  • QoS type - L2 PCP and L3 DSCP
  • Configuration method - VPI verbs and RDMA_CM
  • Verification with ib_write_bw - with options to check if it is the expected configuration
RoCE TrafficQoSConfigurationVerification
RoCEv1L2 PCPVPI verbsSL [0…15]ib_write_bw -S
RDMA_CMToS [0, 8, 24, 16]ib_write_bw -R --tos
RoCEv2L2 PCPVPI verbsSL [0…15]ib_write_bw -S
RDMA_CMToS [0, 8, 24, 16]ib_writte_bw -R --tos
L3 DSCPVPI verbsTClass [0…255]ib_write_bw --tclass
RDMA_CMToS [0…255]ib_write_bw -R --tos

2. Configuration example

This section targets to provide examples for the configuration mentioned above.

2.1. RoCEv2 over Lossless Fabric (ECN+PFC) with Trust L2 QoS

2.1.1. Host configuration

This example provides configuration on host with Redhat 7.4. Dual-port ConnectX-5 is used, and ethernet port ens1f1 is used in the setup.

Enable 8021q Linux kernel module on hosts (for traffic that passes via the kernel, it is not required for RoCE which is kernel bypass)

[root]# modprobe 8021q
[root]# lsmod | grep 8021q
8021q 33208 0
garp 14384 1 8021q
mrp 18542 1 8021q

Set VLAN on hosts

[root]# ip link add link ens1f1 name ens1f1.100 type vlan id 100
[root]# ip link show
23: ens1f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 4200 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether ec:0d:9a:ae:11:dd brd ff:ff:ff:ff:ff:ff
24: ens1f1.100@ens1f1: <BROADCAST,MULTICAST> mtu 4200 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether ec:0d:9a:ae:11:dd brd ff:ff:ff:ff:ff:ff

Set IP for VLAN interface on hosts

[root]# ifconfig ens1f1.100 10.0.0.10

Configure PFC on hosts (enable PFC for priority#3)

[root]# mlnx_qos -i ens1f1 --pfc=0,0,0,1,0,0,0,0

Enable ECN on priority 3 (optional, ECN is enabled by default)

[root]# echo 1 > /sys/class/net/ens1f1/ecn/roce_np/enable/3
[root]# echo 1 > /sys/class/net/ens1f1/ecn/roce_rp/enable/3

Set CNP L2 egress priority on 6 (optional, it is the default value)

[root]# echo 6 > /sys/class/net/ens1f1/ecn/roce_np/cnp_802p_prio

Enable ECN on the TCP traffic (optional, only when it is required for kernel TCP traffic)

[root]# sysctl -w net.ipv4.tcp_ecn=1
net.ipv4.tcp_ecn = 1

Set RoCE mode to V1 for RDMA CM traffic

[root]# cma_roce_mode -d mlx5_1 -p 1 -m 2
RoCE v2

Set default ToS to 24, it is mapped to skprio 4:

[root]# cma_roce_tos -d mlx5_1 -t 24
24

Set Egress priority map (skprio#4 mapped to to user priority#3)

[root]# ip link set dev ens1f1.100 type vlan egress-qos-map 4:3
[root]# cat /proc/net/vlan/ens1f1.100 ens1f1.100 VID: 100 REORDER_HDR: 1 dev->priv_flags: 1
total frames received 0
total bytes received 0
Broadcast/Multicast Rcvd 0
total frames transmitted 0
total bytes transmitted 0
Device: ens1f1
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
EGRESS priority mappings: 4:3

Upon the configuration, the default priority for RoCEv2 has the mapping, it will take effect on RDMC_CM QPs:

ToSSKB PriorityUser PriorityHW Traffic Class
24433

2.1.2. Switch configuration

This example provides configuration on switch with MLNX ONYX, it has port 1/3 and 1/4 used in the setup.

Enable VLAN on switch ethernet interfaces

(config) # vlan 100
(config) # interface ethernet 1/3 switchport mode hybrid
(config) # interface ethernet 1/4 switchport mode hybrid
(config) # interface ethernet 1/3 switchport hybrid allowed-vlan 100
(config) # interface ethernet 1/4 switchport hybrid allowed-vlan 100

Set trust mode on switch ethernet interfaces

(config) # interface ethernet 1/3 qos trust L2
(config) # interface ethernet 1/4 qos trust L2

Create lossless buffer pool on switch

(config) # traffic pool roce_lossless type lossless
(config) # traffic pool roce_lossless memory percent 50.00

Map switch priority 3 to lossless buffer pool

(config) # traffic pool roce_lossless map switch-priority 3

2.1.3. Verification

To verify the settings, generate RoCEv2 traffic on hosts

[server] # ib_write_bw -d [mlx device] -x [GID index] --run_infinitely -R
[client] # ib_write_bw -d [mlx device] -x [GID index] --run_infinitely -R [IP address]

Observe priority-based counters on host:

  • RoCEv2 traffic is expected to be transmitted via priority#3
  • (if any) PFC is expected to be transmitted via priority#3
  • (if any) CNP is expected to be transmitted via priority#6

[root]# ethtool -S ens1f1 | grep prio

Observe priority-based counters on switch ports:

  • RoCEv2 traffic is expected to be transmitted via tc 3
  • (if any) CNP is expected to be transmitted via tc 6

[root]# show interfaces ethernet [switch port] counters tc all

Observe traffic pool-based counters on switch ports, RoCEv2 traffic is expected to be transmitted via pg 1

(config) # show interfaces ethernet [switch port] counters pg all

Observe PFC counters on switch ports, (if any) PFC is expected to be observed in PFC 3

(config) # show interface ethernet [switch port] counters pfc prio all

2.2. RoCEv2 over Lossless Fabric (ECN+PFC) with Trust L3 QoS

2.2.1. Host configuration

This example provides configuration on host with Redhat 7.4. Dual-port ConnectX-5 is used, and ethernet port ens1f1 is used in the setup.

Set trust mode to DSCP on hosts

[root]# mlnx_qos -i ens1f1 –trust=dscp

Set default ToS to 106 (DSCP 26) for all RoCE traffic on the port, it will take effect on QPs created with RDMA_CM and rdma_set_option() is not used by application with option RDMA_OPTION_ID_TOS:

[root]# cma_roce_tos -d [mlx-device] -t 106

Set global TClass to 106 (DSCP 26) for all RoCE traffic on the port, pay attention that it is a global forced value, will be be applied to all QPs, has precedence over cma_roce_tos setting and value specified by user application:

[root]# echo 106 > /sys/class/infiniband/[mlx-device]/tc/1/traffic_class

Rules can be added to QPs for the global forced value. In the example, TClass will be set on loopback traffic with IP address 11.7.156.133:

[root]# echo “src_ip=11.7.156.133/32,dst_ip=11.7.156.133/32,tclass=106” > /sys/class/infiniband/mlx5_0/tc/1/traffic_class

Configure PFC on hosts (enable PFC for priority#3)

[root]# mlnx_qos -i ens1f1 --pfc=0,0,0,1,0,0,0,0

Enable ECN on priority 3 (optional, ECN is enabled by default)

[root]# echo 1 > /sys/class/net/ens1f1/ecn/roce_np/enable/3
[root]# echo 1 > /sys/class/net/ens1f1/ecn/roce_rp/enable/3

Set CNP L3 egress priority on 6 (optional, it is the default value)

[root]# echo 48 > /sys/class/net/ens1f1/ecn/roce_np/cnp_dscp

Enable ECN on the TCP traffic (optional, only when it is required for kernel TCP traffic)

[root]# sysctl -w net.ipv4.tcp_ecn=1
net.ipv4.tcp_ecn = 1

Set RoCE mode to V2 for RDMA CM traffic

[root]# cma_roce_mode -d mlx5_1 -p 1 -m 2
RoCE v2

Upon the configuration, the default priority for RoCEv2 has the mapping, it will take effect on QPs created with VPI verbs and RDMA_CM:

TClassToSDSCPUser PriorityHW Traffic Class
1061062633

2.2.2. Switch configuration

This example provides configuration on switch with MLNX ONYX, it has port 1/3 and 1/4 used in the setup.

Set trust mode on switch ethernet interfaces

(config) # interface ethernet 1/3 qos trust L3
(config) # interface ethernet 1/4 qos trust L3

Create lossless buffer pool on switch

(config) # traffic pool roce_lossless type lossless
(config) # traffic pool roce_lossless memory percent 50.00

Map switch priority 3 to lossless buffer pool

(config) # traffic pool roce_lossless map switch-priority 3

2.2.3. Verification

To verify the settings, generate RoCEv2 traffic on hosts with RDMA_CM QPs

[server] # ib_write_bw -d [mlx device] -x [GID index] --run_infinitely -R
[client] # ib_write_bw -d [mlx device] -x [GID index] --run_infinitely -R [P address]

Or generate RoCEv2 traffic on hosts with QPs created by VPI verbs

[server] # ib_write_bw -d [mlx device] -x [GID index] --run_infinitely
[client] # ib_write_bw -d [mlx device] -x [GID index] --run_infinitely [IP address]

Observe priority-based counters on host:

  • RoCEv2 traffic is expected to be transmitted via priority 3
  • (if any) PFC is expected to be transmitted via priority 3
  • (if any) CNP is expected to be transmitted via priority 6

[root] # ethtool -S ens1f1 | grep prio

Observe priority-based counters on switch ports:

  • RoCEv2 traffic is expected to be transmitted via tc 3
  • (if any) CNP is expected to be transmitted via tc 6

[root]# show interfaces ethernet [switch port] counters tc all

Observe traffic pool-based counters on switch ports, RoCEv2 traffic is expected to be transmitted via pg 1

(config) # show interfaces ethernet [switch port] counters pg all

Observe PFC counters on switch ports, (if any) PFC is expected to be observed in PFC 3

(config) # show interface ethernet [switch port] counters pfc prio all

sunshuying1010
关注
  • 2
    点赞
  • 踩
  • 10
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
RoCE-SAN和RoCE区别
ZJQ的博客
07-15 324
定义：RoCE全称为RDMA over Converged Ethernet，即基于融合以太网的RDMA。RDMA（Remote Direct Memory Access）是一种网络传输技术，允许数据直接在远程计算机的内存中读写，而不需要经过操作系统或CPU的干预，从而降低了延迟并提高了数据传输效率。版本：RoCE有两个主要版本，即RoCE v1和RoCE v2。RoCE v1是链路层协议，通信双方必须在同一个二层网络内；而RoCE v2是网络层协议，支持跨三层网络的路由，具有更好的可扩展性。优势。
RoCEv2网络部署----Mellanox网卡配置
老网工的岁月独白
11-01 5647
mlnx_qos -i ens1np0 -s ets,ets,ets,ets,ets,ets,strict,strict -t 10,10,10,50,10,10,0,0 设置出向队列调度，tc7，tc6严格优先级，tc0-5按权重轮询。mlnx_qos -i ens1np0 -f 0,0,0,1,0,0,0,0 开启priority 3 pfc。mlnx_qos -i ens1np0 -r 0,0,0,0,0,0,30,20 队列限速。设置队列3 PFC，后面打流测试让RoCEv2流量跑在队列3中，
【RDMA】RoCE网络QoS|应用层设置PFC等级|Tos|Priority|TC
小鱼菜鸟的博客
07-22 1544
目录 1.什么是QoS 2.为什么RoCE网络需要QoS 3.为了实现每个流有不同的优先级，硬件层如何对流量分类 4. 应用层如何对流量分类 5. 应用层对流量的分类是怎么映射到硬件层上的分类 6.映射完成之后硬件是怎么针对优先级对网络流进行调度的 6.1 严格优先级 6.2 最小带宽保证(Enhanced Transmission S...
【Mellanox命令系列之mlnx_qos设置DSCP】如何绑定流量类型DSCP与网卡硬件队列，为什么设置，如何生效？（--trust=dscp； --dscp2prio set,63,0）
技术札记
08-11 1104
后2个bit是ECN（显式拥塞通知Explicit Congestion Notification，是用来进行拥塞管理的，数据包从端-交换机-端流程中，流经交换机如果出现交换机拥塞（准确讲是超过交换机配置的认为拥塞的水位线）后，会将该IP报文的ECN字段标记为11，表示数据传输中出现了拥塞，当端侧收到被标记ECN的报文后，接收端会发送一个CNP报文给发送端，以控制发送端进行拥塞控制，进行降速。是针对不同的业务流量，比如会议中的语音和视频，语音更需要保障实时性，那么语音和视频就需要使用不同的优先级传输。
指北系列——vlan使用指北
growdu的网络博客
12-27 660
vlan使用指北 vlan详细内容请参考博客。 VLAN（Virtual Local Area Network）的中文名为"虚拟局域网"。 LAN可以是由少数几台家用计算机构成的网络，也可以是数以百计的计算机构成的企业网络。VLAN所指的LAN特指使用路由器分割的网络——也就是广播域。 简单来说，同一个VLAN中的用户间通信就和在一个局域网内一样，同一个VLAN中的广播只有VLAN中的 成员才能听到，而不会传输到其他的VLAN中去，从而控制不必要的广播风暴的产生。同时， 若没有路由，不同VLAN之间不
【RDMA】设置网卡默认PFC和ECN-在DSCP基于QoS模式下为Linux驱动程序配置ROCE
bandaoyu的note
07-09 2414
本文提供了在安装了MLNX_OFED和Mellanox设备的情况下，针对丢包网络中运行RoCE的DSCP-based QoS模式的配置示例。在使用RDMA-CM时，可以为由RDMA-CM创建的QP设置QoS参数。[可选] 为所有RoCE流量设置ToS为106（DSCP 26）（注：此命令是非持久的）[可选] 将RDMA-CM的ToS设置为106（DSCP 26）（注：此命令是非持久的）[可选] 启用TCP流量的ECN功能（注：此命令是非持久的） 是指mlx设备（例如mlx5_0）
无损网络理论和实践
咸鱼的技术博客
06-13 3865
RDMA技术：降低数据中心内部网络延迟，提高处理效率。当前RDMA在以太网上的传输协议是RoCEv2，RoCEv2是基于无连接协议的UDP协议，相比面向连接的TCP协议，UDP协议更加快速、占用CPU资源更少，但其不像TCP协议那样有滑动窗口、确认应答等机制来实现可靠传输，一旦出现丢包，依靠上层应用检查到了再做重传，会大大降低RDMA的传输效率。
RoCE_with_Priority_Flow_Control_Application_Guide
08-10
在配置RoCE网络时，启用PFC以支持RoCE流量的优先级和QoS控制变得非常重要。配置RoCE时，通常需要在网络设备上（比如交换机）启用PFC，并为RoCE流量设置合适的优先级标记和处理策略。这样可以确保高优先级的RDMA流量...
【RDMA】15. RDMA之RoCE & Soft-RoCE
小鱼菜鸟的博客
09-26 822
【RDMA】RDMA 学习资料总目录_bandaoyu的笔记-CSDN博客SavirRDMA 分享1. RDMA概述https://blog.csdn.net/bandaoyu/article/details/112859853https://zhuanlan.zhihu.com/p/1388747382. 比较基于Socket与RDMA的通信https...
iNOF RoCE-SAN 助力中国银行数字化转型.pdf
12-12
《iNOF RoCE-SAN在数字化转型中的关键作用——以中国银行为例》 随着数字化转型的步伐加速，金融机构，特别是中国银行，正面临着前所未有的挑战与机遇。在2021年的华为智慧金融峰会上，iNOF RoCE-SAN技术被提出作为...
linux命令ip配置vlan,Linux 多IP设置 多vlan设置
weixin_34385935的博客
04-29 2238
Linux 设置 多ip，多vlan引:在Linux下有时候需要给一个网卡绑定多个IP，本文介绍在Redhat系列(redhat,FedoraCore,Centos)中的实现方法和一种在Gentoo等其他Linux中普遍适用的方法。在Linux下有时候需要给一个网卡绑定多个IP，本文介绍在Redhat系列(redhat,FedoraCore,Centos)中的实现方法和一种在Gentoo等其他Li...
提高SPDK高并发的关键--spdk 中的qpair
breaths589的博客
03-30 657
NVME 协议中的qpaire command queue completion queue queue paire SPDK中的qpaire的限制 example/nvme/nvme/hello_world.c中的qpair example/nvme/nvme/perf/perf.c中的qpair 基于qpair提高并发性 ...
某实验中心RDMA RoCE v2 网络实施（100G网络）
最新发布
qq_29109843的博客
08-14 989
QoS RoCE v2 Mellanox NVIDIA
Linux 网络协议栈开发代码分析篇之VLAN（一）—— vlan 功能模块分析
知秋一叶
01-28 5000
整理自：http://blog.csdn.net/lickylin/article/details/41832967 本文代码基于linux3.14       Vlan即虚拟局域网，一个vlan能够模拟一个常规的交换网络，实现了将一个物理的交换机划分成多个逻辑的交换网络。而不同的vlan之间如果要进行通信就要通过三层协议来实现。      在linux中vlan的配置使用vconfig
ip command examples
hjshen1970的专栏
03-11 3204
vlan # ip link add link eth0 name eth0.100 type vlan id 100 Veth ip link add name n1.0.1 type veth peer name n1.0 ip link add name n1.0.1 type veth peer name n1.0 Can # ip link set can0 up t
vlan 划分
wlf_go的博客
03-03 1480
2. ip link 命令格式 括号内为可选内容，小写为参数，直接带入，大写的为占位符，需替换为实际的值 ip link help查看可用的命令： <span style="color:#000000"><span style="background-color:#f3f4f5"><code class="language-bash">Usage: <span style="color:#795da3">ip</span> <span
【Linux命令】ip link
热门推荐
m0_45406092的博客
07-06 1万+
文章目录1. 前言2. ip link 命令格式2.1 ip link add2.1.1 命令实例参考 1. 前言 ifconfig命令已经废弃。其功能可通过下文介绍的ip addr、ip link和ip -s link等命令代替。 常用语法：ip [ OPTIONS ] OBJECT { COMMAND | help } OPTIONS是修改ip行为或改变其输出的选项。所有的选项都是以-字符开头，分为长、短两种形式，常用的OPTIONS： option： -h：输出人类可读的统计信息和后缀 -b：从提供
centos7网络配置（TUI界面配置、nmcli命令配置、修改文件配置）
qq_40301628的博客
10-31 1万+
nmtui
roce2和roce1的差别
06-09
RoCE v2（RDMA over Converged Ethernet version 2）是RoCE协议的第二个版本，相对于RoCE v1（RDMA over Converged Ethernet version 1）有以下几点不同： 1. 传输速度：RoCE v2相对于RoCE v1提高了传输速度，从10Gbps提高到了25Gbps或者更高。 2. 安全性：RoCE v2支持IPsec（Internet Protocol Security）协议来加强数据传输的安全性，可以对数据进行加密和身份验证。 3. 网络拓扑：RoCE v2支持更广泛的网络拓扑结构，可以在传统的数据中心网络、云计算网络、数据湖等不同的网络环境中使用。 4. 网络管理：RoCE v2支持标准化的网络管理协议，如SMI（Subnet Management Interface）和PFC（Priority Flow Control），使得网络管理更加方便和高效。 5. 兼容性：RoCE v2兼容RoCE v1，因此可以在同一个网络中同时使用RoCE v1和RoCE v2设备。 综上所述，RoCE v2相对于RoCE v1在传输速度、安全性、网络拓扑、网络管理和兼容性等方面有了较大的提升，更加适用于高速、安全、可靠的数据传输场景。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值