ARI - Alternative Routing-ID interpretation

最新推荐文章于 2025-05-01 10:28:39 发布
最新推荐文章于 2025-05-01 10:28:39 发布
阅读量859 收藏 2
点赞数
CC 4.0 BY-SA版权
原文链接：http://www.cnblogs.com/lybinger/p/9754158.html
本文深入解析了ARIDevice中16bit RoutingID的组成变化，从传统的Bus-Number、Device-Number及Function-Number三部分，转变为仅由Bus-Number和Function-Number构成，取消了Device-Number，这一改变使ARIDevice能够支持高达256个Function。

16bit的Routing ID以前是由三个部分组成：8bit的Bus-Number，5bit的Device-Number，3bit的Function-Number。

对于ARI Device，这16bit被分成了两个部分：8bit的Bus-Number和8bit的Function-Number，Device-Number没有了，从而使得ARI Device可以支持256个Function。

转载于:https://www.cnblogs.com/lybinger/p/9754158.html

PCIE ARI技术
weixin_40987341的博客
12-02 4983
ARI(Alternative Routing-ID),备选路由ID。在PCIE中，往往数据包传输通过TLP的形式。这些TLP大致分为Memory Read/Write TLP , Configuration Read/Write TLP ,Completion TLP, Message TLP以及IO TLP。这些TLP从Request端到Completion端的过程叫做路由，而路由又大致分为两类地址路由和ID路由。
ProxmoxVE 6.4-13(PVE) 开启SR-IOV INTEL I350-T4 手把手教程
tangobravo的博客
07-29 1万+
首先要在主板中打开SR-IOV选项，华擎以及华硕的绝大部分主板都是支持的，b150这种也可能支持，华擎的有些bios内没有选项，但实际上是支持的 查看网是否正确识别出来，lspci -nn|grep Eth root@AIOserver-Pve:/sys/bus/pci/devices/0000:01:00.0# lspci -nn|grep Eth 00:1f.6 Ethernet controller [0200]: Intel Corporation Device [8086:0d55] 01.
PCIe ARI (Alternative Routing-ID Interpretation)介绍
messi_cyc的专栏
08-13 730
Alternative Routing-ID Interpretation，顾名思义，可替换的Routing ID，意味着这是一种要把Routing ID的部分或全部替换掉的机制。
PCIe 中的 ARI 介绍
日常学习记录
05-01 1354
由于 PCIe 是端对端设备，作为 Endpoint 类型的设备，只有一个 device，即 device number 恒为 0，此时 5-bit 的 Device Number 没有多大意义，而 3-bit Function Number 只能表示 8 个function，在部分虚拟化场景中（例如 SR-IOV），常常不够用。：软件在设置下行端口（Downstream Port）的 ARI Forwarding Enable 位时，必须确保该端口下挂的设备确实支持 ARI 功能。
01:00.0 Ethernet controller: Mellanox Technologies MT2894 Family [ConnectX-6 Lx] Subsystem: Mellanox Technologies Device 0001 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 77 NUMA node: 0 Region 0: Memory at 80002000000 (64-bit, prefetchable) [size=32M] Expansion ROM at e7a00000 [disabled] [size=1M] Capabilities: [60] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 25.000W DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset- MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 16GT/s, Width x8, ASPM not supported ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 16GT/s (ok), Width x8 (ok) TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, NROPrPrP-, LTR- 10BitTagComp+, 10BitTagReq-, OBFF Not Supported, ExtFmt-, EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS-, TPHComp-, ExtTPHComp- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn+ LnkCtl2: Target Link Speed: 16GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [48] Vital Product Data Product Name: ConnectX-6 Lx EN adapter card, 25GbE, Dual-port SFP28, PCIe 4.0 x8, No Crypto Read-only fields: [PN] Part number: MCX631102AN-ADAT [EC] Engineering changes: AC [V2] Vendor specific: MCX631102AN-ADAT [SN] Serial number: MT24476013AM [V3] Vendor specific: 4451ddbdd4a9ef118000b8e924cea95a [VA] Vendor specific: MLX:MN=MLNX:CSKU=V2:UUID=V3:PCI=V0:MODL=CX631102A [V0] Vendor specific: PCIeGen4 x8 [VU] Vendor specific: MT24476013AMMLNXS0D0F0 [RV] Reserved: checksum good, 1 byte(s) reserved End Capabilities: [9c] MSI-X: Enable+ Count=64 Masked- Vector table: BAR=0 offset=00002000 PBA: BAR=0 offset=00003000 Capabilities: [c0] Vendor Specific Information: Len=18 <?> Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ AERCap: First Error Pointer: 08, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: 00000000 00000000 00000000 00000000 Capabilities: [150 v1] Alternative Routing-ID Interpretation (ARI) ARICap: MFVC- ACS-, Next Function: 1 ARICtl: MFVC- ACS-, Function Group: 0 Capabilities: [180 v1] Single Root I/O Virtualization (SR-IOV) IOVCap: Migration-, Interrupt Message Number: 000 IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy+ IOVSta: Migration- Initial VFs: 8, Total VFs: 8, Number of VFs: 0, Function Dependency Link: 00 VF offset: 2, stride: 1, Device ID: 101e Supported Page Size: 000007ff, System Page Size: 00000010 Region 0: Memory at 0000080004800000 (64-bit, prefetchable) VF Migration: offset: 00000000, BIR: 0 Capabilities: [1c0 v1] Secondary PCI Express LnkCtl3: LnkEquIntrruptEn-, PerformEqu- LaneErrStat: 0 Capabilities: [230 v1] Access Control Services ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- Capabilities: [320 v1] Lane Margining at the Receiver <?> Capabilities: [370 v1] Physical Layer 16.0 GT/s <?> Capabilities: [420 v1] Data Link Feature <?> Kernel driver in use: mlx5_core Kernel modules: mlx5_core 以上信息含有：网卡型号解析、数量、ID、带宽、速率、驱动等信息吗
08-20
- ID：PCIe设备ID，通常为15b3:1019（但具体可能因变种而异） - 带宽：支持200Gb/s（即每端口200GbE）或HDR InfiniBand（200Gb/s） - 速率：支持多种速率，包括10G、25G、40G、50G、100G、200G以太网和HDR ...
pcie的ARI能力是什么
07-09
PCIe（PCI Express）的ARI（Alternative Routing-ID Interpretation，替代路由ID解析）是一种用于优化PCIe设备寻址和配置的技术，主要用于支持多设备共享单一功能号（Function Number）的场景，尤其在SR-IOV（Single...
我“lspci -v”返回 “0000:00:00.0 Class 0604: Device 19e5:1230 (rev 21) Flags: bus master, fast devsel, latency 0, IRQ 93 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: 00800000-047fffff [size=64M] [32-bit] Prefetchable memory behind bridge: b04800000-b087fffff [size=64M] [32-bit] Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/32 Maskable+ 64bit+ Capabilities: [b0] Power Management version 3 Capabilities: [d0] Subsystem: Device ffff:1230 Capabilities: [100] Advanced Error Reporting Capabilities: [310] Secondary PCI Express Capabilities: [3c0] L1 PM Substates Capabilities: [630] Access Control Services Kernel driver in use: pcieport lspci: Unable to load libkmod resources: error -2 0005:00:00.0 Class 0604: Device 19e5:1230 (rev 21) Flags: bus master, fast devsel, latency 0, IRQ 94 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: a0800000-a47fffff [size=64M] [32-bit] Prefetchable memory behind bridge: ba4800000-ba87fffff [size=64M] [32-bit] Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/32 Maskable+ 64bit+ Capabilities: [b0] Power Management version 3 Capabilities: [d0] Subsystem: Device ffff:1230 Capabilities: [100] Advanced Error Reporting Capabilities: [310] Secondary PCI Express Capabilities: [3c0] L1 PM Substates Capabilities: [630] Access Control Services Kernel driver in use: pcieport 0005:01:00.0 Class 0108: Device 1e4b:1202 (rev 01) (prog-if 02) Subsystem: Device 1e4b:1202 Physical Slot: 0-1 Flags: bus master, fast devsel, latency 0, NUMA node 0 Memory at ba0800000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 1f Capabilities: [b0] MSI-X: Enable+ Count=9 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [148] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [158] Alternative Routing-ID Interpretation (ARI) Capabilities: [168] Secondary PCI Express Capabilities: [1d4] Latency Tolerance Reporting Capabilities: [1dc] L1 PM Substates Capabilities: [1ec] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?> Capabilities: [2ec] Vendor Specific Information: ID=0001 Rev=1 Len=038 <?> Kernel driver in use: nvme 0007:00:00.0 Class 0604: Device 19e5:1230 (rev 21) Flags: bus master, fast devsel, latency 0, IRQ 104 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: e0800000-e47fffff [size=64M] [32-bit] Prefetchable memory behind bridge: be4800000-be87fffff [size=64M] [32-bit] Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/32 Maskable+ 64bit+ Capabilities: [b0] Power Management version 3 Capabilities: [d0] Subsystem: Device ffff:1230 Capabilities: [100] Advanced Error Reporting Capabilities: [310] Secondary PCI Express Capabilities: [3c0] L1 PM Substates Capabilities: [630] Access Control Services Kernel driver in use: pcieport ” 请帮我分析我的log，是否挂上了pcie的设备，以及log中的 “lspci: Unable to load libkmod resources: error -2”是什么意思
最新发布
09-02
- **设备 ID 和描述**：例如 `00:02.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)`。 - **状态信息**：如 `Kernel driver in use: nvidia` 或 `Kernel modules: nvidia`，表示驱动程序...
新鲜出炉的PCI-E协议3.0
12-01
2.2.4. Routing and Addressing Rules.............................................................................. 60 2.2.5. First/Last DW Byte Enables Rules..............................................
【PCIe 5.0 - 9】PCIe 事务层详解5 - 事务描述符
BGONE的博客
12-23 3843
Transaction Descriptor
PCIE 学习笔记一
weixin_43986267的博客
06-29 1362
PCIE transaction layer
【PCIe 5.0 - 6】PCIe 事务层详解2 - 带Data Payloads的TLP封装规则
BGONE的博客
12-17 1713
带Data Payloads的TLP封装规则
5.3 存储器、I/O和配置读写请求TLP 分类： 浅谈PCI-E ...
weixin_30347335的博客
07-22 784
本节讲述PCIe总线定义的各类TLP，并详细介绍这些TLP的格式。在这些TLP中，有些格式对于初学者来说较难理解。读者需要建立PCIe总线中与TLP相关的一些基本概念，特别是存储器读写相关的报文格式。在PCIe总线中，存储器读写，I/O读写和配置读写请求TLP由以下几类报文组成。 (1) 存储器读请求TLP和读完成TLP 当PCIe主设备，RC或者EP，访问目标设备...
沧小海笔记之PCIE协议解析——第二章 详述PCIE事务层
滄海的博客
04-12 9782
总目录在此哦~ https://blog.youkuaiyun.com/z123canghai/article/details/115644744 目录 2.1 内容概述 2.2 PCIE的事务类型 2.2.1 通用帧头 2.2.2 内存事务 2.2.3 完成事务 2.2.4 配置事务 2.3事务传输方式 2.3.1 Non-Posted事物类型 2.3.2 Posted事物类型 2.3.3 一个案例 2.1 内容概述 本章节的主要内容如下所示。 2.1内容概述...
linux查看网卡型号、驱动版本、队列数
热门推荐
swrd
01-05 2万+
一、如何查看网卡生产厂家和型号？  lspci命令   查看基本信息 lspci， 详细信息lspci -vvv   00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 13) 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O
PCIe扫盲——TLP路由之ID Routing
kunkliu的博客
07-01 2554
转载地址：http://blog.chinaaet.com/justlxy/p/5100053324 ID 路由（ID Routing）有的时候也被称为BDF路由，即采用Bus Number、Device Number和Function Number来确定目标设备的位置。这是一种兼容PCI和PCI-X总线协议的路由方式，主要用于配置请求（Configuration Request）的路由，在PC...
PCIe资料汇总
叶玄青的博客
05-30 1万+
整理PCIe相关知识及资料
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值