Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberCN1547704 A
Publication typeApplication
Application numberCN 02816580
PCT numberPCT/US2002/027042
Publication date17 Nov 2004
Filing date23 Aug 2002
Priority date24 Aug 2001
Also published asCN1547705A, CN1547823A, CN100357922C, CN100367254C, CN100409606C, DE60213616D1, DE60213616T2, DE60222782D1, DE60226627D1, EP1419446A1, EP1419446B1, EP1421501A1, EP1421501B1, EP1442548A2, EP1442548B1, US7152128, US7231486, US7353313, US7536473, US8566473, US8819306, US9049125, US9071528, US9088495, US9565106, US9602408, US9736071, US20030115380, US20030145134, US20030158992, US20070038793, US20090193164, US20130117474, US20130254451, US20130254452, US20130268712, US20140129747, US20140185436, US20140189174, US20150178241, WO2003019391A2, WO2003019391A3, WO2003019393A1, WO2003019394A1
Publication number02816580.2, CN 02816580, CN 1547704 A, CN 1547704A, CN-A-1547704, CN02816580, CN02816580.2, CN1547704 A, CN1547704A, PCT/2002/27042, PCT/US/2/027042, PCT/US/2/27042, PCT/US/2002/027042, PCT/US/2002/27042, PCT/US2/027042, PCT/US2/27042, PCT/US2002/027042, PCT/US2002/27042, PCT/US2002027042, PCT/US200227042, PCT/US2027042, PCT/US227042
Inventors贾斯明·阿亚诺维奇, 贾斯明・阿亚诺维奇, J・哈里曼, 戴维·J·哈里曼, ・L・坎贝尔, 伦道夫·L·坎贝尔, A・瓦尔加斯, 乔斯·A·瓦尔加斯, 克利福德·霍尔, 德・霍尔, 安特・塞西, 普拉沙安特·塞西, ・帕夫洛夫斯基, 史蒂夫·帕夫洛夫斯基
Applicant英特尔公司
Export CitationBiBTeX, EndNote, RefMan
External Links: SIPO, Espacenet
A general input/output architecture, protocol and related methods to support legacy interrupts
CN 1547704 A
Abstract  translated from Chinese
本发明公开了一种增强型通用输入/输出通信体系结构、协议以及相关的方法。 The present invention discloses a method for enhanced general input / output communication architecture, protocol and related methods.
Claims(30)  translated from Chinese
1.一种将老式设备集成在增强型通用输入/输出体系结构中的方法,所述方法包括:从位于通用输入/输出接口的老式设备接收指示;分析所述所接收指示的至少一个子集以识别指示符类型;以及基于或至少部分基于所述分析的结果,将所述所接收的老式指示转换为适合的一个或多个通用输入/输出消息。 An old equipment will be integrated in an enhanced general input / output architecture, the method comprising: from in the general input / output interface of the old equipment received instructions; analyzing at least a subset of the received indication to identify the type indicator; and based at least in part based on the results of the analysis, the received instructions to convert the old one or more suitable for general-purpose input / output messages.
2.如权利要求1所述的方法,还包括:根据与所述通用输入/输出消息相关联的一组规则处理所述通用输入/输出消息。 2. The method of claim 1, further comprising: the general-purpose input / output messages to a set of rules associated with processing the general-purpose input / output messages.
3.如权利要求2所述的方法,所述处理步骤包括:识别所述通用输入/输出接口的主机是否是所述通用输入/输出消息的目标;以及如果所述所识别的目标不是所述主机,则将所述通用输入/输出消息通过通用输入/输出链路转发到所述所识别的目标。 3. The method of claim 2, wherein said processing step comprises: identifying the general purpose input / output interface, whether the host is the target of the general-purpose input / output messages; and if the goal is not identified the host, then the general-purpose input / output message to the identified goals through general-purpose input / output links.
4.如权利要求3所述的方法,所述转发步骤包括将所述通用输入/输出消息写入远程通用输入/输出接口的消息空间,所述远程通用输入/输出接口通过通用输入/输出接口链路可通信地与所述通用输入/输出接口相耦合。 4. The method of claim 3 through a common input / output interface of claim step includes the general-purpose input / output messages written to the remote general input / output interface, the forwarding message space, the remote general input / output interface Link can communicate with the general-purpose input / output interface coupled.
5.如权利要求1所述的方法,其中所述指示是老式中断。 5. The method of claim 1, wherein said indication is the old interrupt.
6.如权利要求5所述的方法,其中所述指示是外围组件互连中断。 6. The method according to claim 5, wherein the indication is a peripheral component interconnect interrupt.
7.如权利要求1所述的方法,其中所述指示是电源管理请求。 7. The method of claim 1, wherein said indication is a power management request.
8.如权利要求7所述的方法,其中所述电源管理请求是热插拔通知。 8. The method of claim 7, wherein the power management request is a hot-plug notification.
9.如权利要求1所述的方法,其中所述所接收的指示是特殊周期请求。 9. The method of claim 1, wherein the received indication is a special cycles request.
10.如权利要求1所述的方法,所述分析所述所接收指示的至少一个子集的步骤包括:将所述所接收的指示与由所述通用输入/输出接口维护的一个或多个已知老式指示相比较以分析所述所接收的指示的含义。 10. The method of claim 1, wherein said analyzing step of receiving an indication of at least one of the subset comprises: one or more of the received instructions by said general purpose input / output interface maintenance known in the old compared to the analysis indicates the meaning of the received indication.
11.如权利要求1所述的方法,所述转换步骤包括:识别与通用输入/输出协议相关联的代码,所述通用输入/输出协议由传递所述所接收指示的含义的所述通用输入/输出体系结构使用;以及合成包括所述代码的消息以发送到所述所接收指示的所识别目标。 11. The method of claim 1, wherein the conversion step includes: a code identification and general purpose input / output protocol associated with the general-purpose input / output protocols by the transfer of the received indication of the meaning of universal input I / O architecture uses; and synthetic includes the code to send messages to the received indication of the identified target.
12.如权利要求11所述的方法,其中所述所接收指示的所述所识别目标是所述通用输入/输出接口的主机。 12. The method of claim 11, wherein said received indication of said target is identified by the host general-purpose input / output interface.
13.如权利要求11所述的方法,其中所述所接收指示的所述所识别目标是通过一个或多个通用输入/输出链路而被耦合的远程设备。 13. The method of claim 11, wherein said received indication of said target is identified by one or more general input / output link being coupled to the remote device.
14.如权利要求11所述的方法,其中所述所接收指示被识别为外围组件互连中断,所述合成步骤包括:生成指明所述所识别中断的断言的消息,用于如所需地通过所述通用输入/输出体系结构向所述中断的目标发送。 14. The method of claim 11, wherein the received indication is identified as a peripheral component interconnect interrupt, the synthesis step comprises: generating an assertion indicating the interrupted message identification to be used as desired I / O architecture is sent to the interrupt target by the general-purpose input.
15.如权利要求12所述的方法,还包括:在接收到指明终止所述中断的指示之后,生成指明所述所识别中断的反断言的消息,用于如所需地通过所述通用输入/输出体系结构向所述中断的目标发送。 15. The method as recited in claim 12, further comprising: after receiving an indication indicating the termination of the interrupt generated by the deasserted indicating message identifying the interrupt used as desired by the general-purpose input I / O architecture of the transmit interrupt to the target.
16.如权利要求15所述的方法,其中所述终止所述中断是指明终止所述中断的指示。 16. The method of claim 15, wherein said terminating said interrupt is specified to terminate said interrupt instructions.
17.一种通用输入/输出接口,包括:物理层接口,通过通用输入/输出链路将所述通用输入/输出接口耦合到远程接口;和事务层接口,接收从所述远程接口接收的包括老式内容的内容的至少一个子集,其中所述事务层基于或至少部分基于适合由主设备或远程设备进行附加处理的所述老式内容生成通用输入/输出消息。 17. A general-purpose input / output interfaces, including: a physical layer interface, through the universal input / output links to the general-purpose input / output interface is coupled to the remote interface; and Transaction Layer interface, receiving received from the remote interface includes at least a subset of the content of the old content, wherein the transaction layer or at least partially based on suitable for additional processing by the master device or a remote device the old content generation general-purpose input / output messages.
18.如权利要求17所述的通用输入/输出接口,其中所述远程接口包括与老式设备或增强型通用输入/输出设备相关联的老式接口。 18. The claim 17 general purpose input / output interface, wherein the remote interface includes the old equipment or enhanced general-purpose input / output device associated with the old interface.
19.如权利要求17所述的通用输入/输出接口,所述事务层接口包括:包括消息空间的数据结构,其中通用输入/输出接口的所述事务层将所述所生成的通用输入/输出消息写入远程通用输入/输出接口。 19. The claim 17 general purpose input / output interface, the transaction layer interface comprising: a data structure of the message space, wherein the transaction layer general purpose input / output interfaces generated by the universal input / output Messages written to the remote general input / output interface.
20.如权利要求19所述的通用输入/输出接口,其中所述通用输入/输出消息引起所述远程通用输入/输出接口向目标设备转发所述通用输入/输出消息。 20. 19 general-purpose input / output interface wherein the general-purpose input / output message causes the remote general input / output interface to forward the general input / output message to the target device.
21.如权利要求20所述的通用输入/输出接口,其中所述远程通用输入/输出接口是所述目标设备的元件。 21. The claim 20 general purpose input / output interface, wherein the remote general input / output interface is a member of the target device.
22.如权利要求20所述的通用输入/输出接口,其中所述通用输入/输出消息引起所述目标设备根据所述老式内容工作。 22. The universal input 20 / output interface wherein the general-purpose input / output messages cause the target device to work in accordance with the old content.
23.如权利要求19所述的通用输入/输出接口,所述数据结构包括:配置空间,用于维护信息以指明主设备类型;和消息空间,用于帮助在通用输入/输出体系结构中的通用输入/输出接口之间带内传送表示老式内容的通用输入/输出消息。 23. 19 general-purpose input / output interface of claim data structure comprising: a configuration space for maintenance information to indicate that the primary device type; and news space for help in the general-purpose input / output architecture Universal Input zone between the general-purpose input / output interface represents the old contents of the delivery / output messages.
24.如权利要求17所述的通用输入/输出接口,其中所述老式接口与外围组件互连兼容设备相关联。 24. The input 17 of the universal / output interface as claimed in claim wherein the interface with the old peripheral component interconnect compliant device is associated.
25.如权利要求17所述的通用输入/输出接口,其中所述老式内容包括中断、电源管理消息和特殊周期请求中的一个或多个。 25. 17 general-purpose input / output interface wherein the old content including interrupt, power management news and special cycle request of one or more.
26.一种电子设备,包括如权利要求17所述的通用输入/输出接口。 26. An electronic device comprising of claim 17, wherein the general-purpose input / output interface.
27.一种电子装置,包括:多个如权利要求26所述的电子设备,有选择地与通用输入/输出通信链路相耦合;和零个或多个老式设备,每个都有选择地耦合到所述多个电子设备的相关联的一个,其中所述相关联的电子设备基于或至少部分基于从相关联的老式设备接收的老式内容生成通用输入/输出消息。 27. An electronic device, comprising: a plurality of electronic equipment such as 26 claim, selective and general purpose input / output coupled to a communication link; and zero or more of the old equipment, each selectively coupled to one associated with the plurality of electronic devices wherein the associated electronic equipment based at least in part based on the old equipment received from the associated content generation old general-purpose input / output messages.
28.一种包括内容的存储介质,当所述内容由访问电子设备执行时,引起所述电子设备实现通用输入/输出接口,所述通用输入/输出接口包括物理层接口,用于通过通用输入/输出链路将所述通用输入/输出接口耦合到远程接口,和事务层接口,用于接收从所述远程接口接收的包括老式内容的内容的至少一个子集,其中所述事务层基于或至少部分基于适合由主设备或远程设备进行附加处理的所述老式内容来生成通用输入/输出消息。 28. A including the contents of the storage medium, when the content of the access to an electronic device to perform, cause the electronic equipment to achieve universal input / output interface, the universal input / output interface includes a physical layer interface for input by Universal I / O link to the general-purpose input / output interface is coupled to the remote interface, and transaction layer interface for receiving received from the remote interface comprises at least a subset of the content of the old content, wherein the transaction layer is based on or Based at least in part for additional processing by the master device or a remote device to generate the contents of the old general-purpose input / output messages.
29.如权利要求28所述的存储介质,实现所述事务层的所述内容还包括将所接收的老式内容转换为上行流通用输入/输出接口可理解的通用输入/输出消息的内容。 29. The storage medium of claim 28, wherein the content of the transaction layer to achieve further comprises the received uplink old content into circulation with the contents of the input / output interface comprehensible general input / output message.
30.如权利要求29所述的存储介质,其中所述老式内容包括中断、电源管理消息和特殊周期请求的一个或多个。 30. The storage medium according to claim 29, wherein the content includes interruption old, one or more power management message and the special cycle request.
Description  translated from Chinese
支持老式中断的通用输入/输出体系结构、协议和方法 Vintage interrupt support general-purpose input / output architecture, protocols and methods

优先权本申请明确地要求了由Ajanovic等人于2001年8月24日递交的美国临时申请No.60/314,708,名为“A High-speed,Point-to-PointInterconnection and Communication Architecture,Protocol and RelatedMethods”(“高速、点到点互连和通信体系结构、协议以及相关方法”)的优先权,并且转让给本申请的受让人。 PRIORITY This application claims the United States explicitly provisional application by the Ajanovic et al. August 24, 2001, filed No.60 / 314,708, entitled "A High-speed, Point-to-PointInterconnection and Communication Architecture, Protocol and RelatedMethods "(" high-speed, point to point interconnect and communications architecture, protocol and related methods "), priority, and assigned to the assignee of the present application.

技术领域 Technical Field

本发明一般地涉及通用输入/输出(GIO)总线体系结构领域,更具体地说,本发明涉及一种体系结构、协议以及相关的方法,用来在GIO总线体系结构中的元件之间支持老式中断。 The present invention generally relates to general purpose input / output (GIO) bus architecture field, and more particularly, the present invention relates to an architecture, protocol and related methods, support among older GIO bus architecture used in the element interruption.

背景技术 Background

计算装置例如计算机系统、服务器、网络交换机和路由器、无线通信设备以及其它电子设备一般由许多电子组件或元件组成。 Computing device such as a computer system, server, network switches and routers, wireless communication devices and other electronic equipment typically consists of many electronic components, or components. 这些元件通常包括处理器、微控制器或其它控制逻辑、存储器系统、(多个)输入和输出接口、外围元件等。 These elements generally include a processor, microcontroller or other control logic, memory system (s) of input and output interfaces, peripheral components. 为了便于这些元件之间的通信,计算装置长期依赖于通用输入/输出(GIO)总线体系结构,以使得该计算装置的这些根本不同的元件能够互相通信来支持由这样的装置提供的种种应用。 In order to facilitate communication between these elements, computing devices rely on general-purpose input / output (GIO) bus architecture to enable these disparate elements of the computing device capable of communicating with each other to support a variety of applications by such means.

这种传统的GIO总线体系结构最普遍的一种形式或许就是外围组件互连总线或PCI总线体系结构。 Such a form of conventional GIO bus architecture is perhaps the most common peripheral component interconnect bus or PCI bus architecture. PCI总线标准(1998年12月18日发布的外围组件互连(PCI)局域总线规范,修订版2.2)规定了多接点式(multi-drop)、并行总线体系结构,用于在计算装置中以仲裁的方式来互连芯片、扩充板以及处理器/存储器子系统。 Standard PCI bus (Peripheral Component Interconnect December 18, 1998 release (PCI) Local Bus Specification, Revision 2.2) provides a multi-contact-type (multi-drop), parallel bus architecture for computing devices by means of arbitration to interconnect chips, expansion boards, and processor / memory subsystem. 为了本发明的目的,PCI局域总线标准的内容在这里作为参考而被明确地引用。 For purposes of the present invention, the content of the PCI local bus standard is herein expressly incorporated by reference.

传统的PCI总线实现具有133兆字节每秒的吞吐量(即,33兆赫兹32字节),而PCI 2.2标准允许每个管脚64字节的并行连接,时钟达到133MHz,从而产生超过1GBps的理论吞吐量。 The traditional PCI bus realize a throughput of 133 megabits per second (ie, 33 MHz 32 bytes), and PCI 2.2 standard allows each pin parallel connection of 64 bytes, the clock reaches 133MHz, resulting in more than 1GBps The theoretical throughput. 在这方面,由这样的传统多接点式PCI总线体系结构提供的吞吐量到目前为止已经提供了足够的带宽来适应即使是最先进的计算装置(例如,多处理器服务器应用、网络装置等)的内部通信需要。 In this regard, provided by such conventional multi-drop style throughput PCI bus architecture has so far provided enough bandwidth to accommodate even the most advanced computing devices (for example, multiprocessor server applications, network devices, etc.) internal communications needs. 然而,联系到宽带因特网访问的广泛应用,处理能力的新近进展将处理速度超过了1GHz的阈值,诸如PCI总线体系结构的传统GIO体系结构已经变成这样的计算装置中的瓶颈。 However, linked to the widespread use of broadband Internet access, recent progress in processing speed processing capability will exceed the threshold of 1GHz, traditional GIO architectures such as PCI bus architecture has become such a computing device bottlenecks.

通常与传统GIO体系结构联系在一起的另一个限制是,它们通常不能很好的适宜于操作/处理同步(或者说时间相关)数据流。 Usually associated with conventional GIO architectures together Another limitation is that they are generally not well adapted to the operation / process synchronization (or time-dependent) data streams. 这样的同步数据流的一个例子是多媒体数据流,该多媒体数据流需要同步传输机制来确保接收数据与使用数据同速,并且音频部分与视频部分同步。 An example of such a synchronous data stream is multimedia data streams, multimedia data stream which requires a transport mechanism to ensure that the received synchronization data with the use of data at the same speed, and the audio portion is synchronized with the video portion.

传统的GIO体系结构异步处理数据,或以带宽允许的随机时间间隔处理数据。 Conventional GIO architectures process data asynchronously, or bandwidth allows the processing of data at random intervals. 这种同步数据的异步处理可能导致音频与视频的不重合,作为结果,某些同步多媒体内容供应商制定了使某些数据优先于其它数据的规则,例如使音频数据优先于视频数据,从而最终用户至少接收相对稳定的音频流(即,不被打断),使得他们可以欣赏或了解正在被流式播放的歌曲、故事等等。 Such asynchronous processing of isochronous data can result in audio and video do not coincide, as a result, some of the synchronized multimedia content providers to develop a data take precedence over the rules of certain other data, e.g., so that the audio data in preference to the video data, so that the final Users receive at least relatively stable audio stream (ie, without interruption), so they can appreciate or understand being streamed songs, stories and so on.

附图说明 Brief Description

本发明以示例而非限制的方式被说明,附图中类似的标号指示类似的元件,并且其中:图1是电子装置的方框图,该电子装置包括本发明的实施例的一个或多个方面以便于该装置的一个或多个组成元件之间的通信;图2是根据本发明一个示例性实施例的示例性通信栈的示图,该通信栈由电子装置的一个或多个元件使用以便于这些元件之间的通信;图3是根据本发明教导的示例性事务层(transaction layer)数据报的示图;图4是根据本发明一个方面的示例性通信链路的示图,该通信链路包括一个或多个虚拟信道以便于电子设备的一个或多个元件之间的通信;图5是根据本发明一个实施例,用于在EGIO(增强型通用输入/输出)体系结构中提供同步通信资源的示例性方法的流程图;图6是根据本发明的一个方面,用于在EGIO体系结构中实现流控制的示例性方法的流程图;图7是根据本发明的一个方面,用于在EGIO体系结构中实现数据完整性特征的示例性方法的流程图;图8是根据本发明的一个示例性实施例的示例性通信代理的方框图,以选择性实现本发明的一个或多个方面;图9是本发明的事务层中使用的各种分组头部格式的方框图;图10是根据本发明示例性实施例的示例性存储器体系结构的方框图,该存储器体系结构被用于帮助本发明的一个或多个方面;图11是根据本发明一个方面的示例性链路状态机图的状态图;以及图12是含有内容的可访问介质的方框图,所述内容当由电子设备访问时实现本发明的一个或多个方面。 The present invention of example and not by way of limitation is illustrated, the accompanying drawings in which like reference numerals indicate like elements, and wherein: FIG. 1 is a block diagram of an electronic device, the electronic device comprises an embodiment of the present invention, one or more aspects in order to one or more elements of the apparatus of the communication between the composition; FIG. 2 is an exemplary communications stack to an exemplary embodiment of the present invention illustrating the communication stack is used by an electronic device or a plurality of elements in order to Communication between these elements; Figure 3 is an example of the present teachings transaction layer (transaction layer) illustration of the data reported; Figure 4 is an illustration of one aspect of the present invention, an exemplary communication link, the communication chain path includes one or more virtual channels for communication between the electronic device or a plurality of elements; Fig. 5 is an embodiment of the present invention for providing synchronization (Enhanced General Purpose Input / Output) in the EGIO architecture flowchart of an exemplary method of communication resources; Figure 6 is in accordance with one aspect of the present invention, for controlling the flow of a flowchart of an exemplary method implemented in the EGIO architecture; Fig. 7 is in accordance with one aspect of the present invention, for flowchart of an exemplary method implemented in the EGIO architecture of data integrity feature; Figure 8 is a block diagram of an exemplary communication agent of the present invention according to an exemplary embodiment, in order to achieve a selective or more aspects of the present invention, ; Figure 9 is a block diagram of the various transaction layer packet header format used in the present invention; FIG. 10 is a block diagram of an exemplary memory architecture according to an exemplary embodiment of the present invention, the memory architecture of the present invention is used to help of one or more aspects; Figure 11 is an aspect of the present invention, an exemplary link state machine diagram of a state; and Figure 12 is a block diagram containing content accessible medium, the content of the electronic device when implementing accessed by one or more aspects of the present invention.

具体实施方式 DETAILED DESCRIPTION

本发明的多个实施例一般地涉及通用输入/输出(GLO)体系结构、协议和相关方法,以实现支持通用输入/输出接口组件之间的老式中断。 A plurality of embodiments of the present invention generally relates to general purpose input / output (GLO) architecture, protocol and related methods, in order to achieve support for the old general purpose input / output interface module is interrupted. 在这方面,介绍了创新的增强型通用输入/输出(EGIO)互连体系结构、相关通信协议和有关方法。 In this regard, we introduced an innovative enhanced general input / output (EGIO) interconnection architecture, associated communication protocol and related methods. 根据一个示例性实施例,EGIO体系结构的元件包括根复合体(root complex)(例如,在桥内实现)、以及端点(endpoint)中的一个或多个,每个元件至少包含EGIO特征的一个子集以支持这些元件之间的EGIO通信。 According to an exemplary embodiment, element EGIO architecture include root complex (root complex) (e.g., in the realization of the bridge), and the endpoint (endpoint) in one or more of each of the elements comprising at least one EGIO features subset to support EGIO communication between these elements.

使用(多条)串行通信信道来执行这些元件的EGIO设备之间的通信,所述串行通信信道使用EGIO通信协议,所述协议如下面将要详细介绍的那样支持一个或多个创新特征,所述特征包括但不局限于虚拟通信信道、基于尾部(tailer)的错误转发(error forwarding)、对老式(legacy)的基于PCI的设备及其中断的支持、多种请求响应类型、流控制和/或数据完整性管理功能。 Use (s) serial communications channel to perform communication between these elements EGIO device, said serial communications channel using the EGIO communication protocol, the protocol as will that supports one or more innovative features to be described in detail, The features include, but are not limited to virtual communication channel, forward (error forwarding) based on the tail (tailer) errors of old (legacy) of the PCI device and its interrupt-based support, multiple request response type, flow control, and / or data integrity management. 根据本发明的一个方面,通过引入EGIO通信协议栈,在每个计算装置的元件中都支持了通信协议,该栈包括物理层、数据链路层和事务层。 According to one aspect of the present invention, by introducing EGIO communication protocol stack, the elements of each computing device supports the communication protocol stack, including the physical layer, data link layer and transaction layer.

在本说明书各处提及的“一个实施例”或“实施例”指的是,所描述的与该实施例有关的具体特征、结构或特性被包括在本发明的至少一个实施例中。 "One embodiment" or "an embodiment" in various places throughout this specification refers to the mention of the specific features associated with the embodiment described, structure, or characteristic is included in at least one embodiment of the present invention. 因此,在本说明书多个位置出现的短语“在一个实施例中”或“在实施例中”不必都指同一个实施例。 Therefore, in this specification multiple locations appears on the phrase "in one embodiment" or "in an embodiment" are not necessarily all referring to the same embodiment. 此外,所述具体特征、结构或特性可以适当的方式结合在一个或多个实施例中。 Furthermore, the particular features, structures or characteristics may be combined in a suitable manner with one or more embodiments.

根据前述内容和下面的描述,本领域技术人员应当意识到,本发明的一个或多个元件可以容易地以硬件、软件、传播的信号或它们的组合来实现。 From the foregoing and the following description, one skilled in the art would recognize that one or more elements of the present invention can be easily implemented in hardware, software, communication signals or a combination thereof to achieve.

术语在深入讨论创新的EGIO互连体系结构、通信协议和相关方法的细节之前,引入将在该详细描述中使用的词汇表元素是很有帮助的:·通告(Advertise):在EGIO流控制的上下文中使用,是指通过使用EGIO协议的流控制更新消息来指示接收器发送有关它的流控制信用(credit)可用性的信息的动作;·完成器(Completer):请求所指向的逻辑设备;·完成器ID:完成器的总线标识符(例如,号码)、设备标识符和功能标识符中的一个或多个的组合,其唯一标识了请求的完成器;·完成(completion):用于终止或部分终止一个序列的分组被称为完成。 The term in-depth discussion before the details of innovative EGIO interconnection architecture, communication protocol and related methods, the introduction of vocabulary elements used in the detailed description can be helpful: · Announcements (Advertise): In EGIO flow control used in this context, it refers to the protocol by using the EGIO flow control update message to indicate that the receiver sends action relating to its flow control credit (credit) availability of information; · complete device (Completer): the request is directed logical device; · complete device ID: complete the bus identifier (for example, number), device identifier and function identifiers of one or a combination of multiple, which uniquely identifies the completion of the request; a * complete (completion): used to stop or partial termination of a sequence of packets is called complete. 根据一个示例性实现,完成对应于在前请求,并且在某些情况下含有数据;·配置空间:EGIO体系结构中的四个地址空间中的一个。 According to an exemplary implementation, corresponding to the previous request is completed, and the data contained in some cases; * configuration space: EGIO architecture, four address space a. 具有配置空间地址的分组被用于配置设备;·组件:物理设备(即,在单个封装之中);·数据链路层:EGIO体系结构的中间层,位于事务层(上层)和物理层(下层)之间; Packet has the configuration space address are used to configure the device; · components: physical devices (ie, in a single package being); • Data link layer: intermediate layer EGIO architecture, located transaction layer (upper layer) and physical layer ( between lower);

·数据链路层分组(DLLP):数据链路层分组是在数据链路层产生并使用的分组,来支持在数据链路层处执行的链路管理功能;·下行流(downstream):指的是元件的相对位置或离开主桥的信息流;·端点:具有00h类型配置空间头部的EGIO设备;·流控制:用于将来自接收器的接收缓冲器信息发送到发送器,以防止接收缓冲器溢出,并且允许发送器装置服从排序规则;·流控制分组(FCP):事务层分组,用于将来自一个组件中的事务层的流控制信息发送到另一个组件中的事务层;·功能:多功能设备的一个独立部分,在配置空间中由唯一的功能标识符(例如,功能号码)标识;·层次(Hierarchy):定义了在EGIO体系结构中实现的I/O互连拓扑结构。 · Data link layer packet (DLLP): data link layer packet is a packet in the data link layer is generated and used to support the implementation of the data link layer link management function; · downstream (downstream): means The relative position or away from the main stream of the bridge element; * endpoint: a type 00h configuration space header EGIO device; * Flow control: buffer means for transmitting and receiving information from the receiver to the transmitter, to prevent receive buffer overflow and allows the sending device subject to collation; · flow control packet (FCP): transaction layer packet for flow from one component of the transaction layer control information to another component of the transaction layer; • Function: an independent part of a multifunction device, in the configuration space is identified by a unique function identifier (for example, feature numbers); · Hierarchy (Hierarchy): defines the EGIO architecture to achieve I / O interconnect topology structure. 层次由对应于最靠近枚举设备(enumerating device)(例如,主CPU)的链路的根复合体来表征;·层次域:EGIO层次被根复合体分成多个段,所述根复合体产生不只一个EGIO接口,其中这些段被称为层次域;·主桥:将主CPU复合体连接到根复合体;主桥可以提供根复合体;·IO空间:EGIO体系结构的四个地址空间中的一个;·管线(Lane):物理链路的一组差分信号对,一对用于发送并且一对用于接收。 The level corresponding to the closest enumeration equipment (enumerating device) (for example, the main CPU) of the root complex to characterize link; · level domain: EGIO hierarchy is the root of the complex is divided into a plurality of segments, the root complex to produce more than one EGIO interfaces, these segments are known as level domain; · Main Bridge: The complex is connected to the main CPU root complex; the main bridge can provide root complex; · IO space: EGIO architecture of the four address space A; · Pipeline (Lane): A set of physical links differential signal pairs, one pair for transmitting and one pair for receiving. N链路由N条管线组成;·链路:两个组件之间的双单工(dual-simplex)通信路径;两个端口(一个发送,一个接收)的集合以及它们的(多条)互连管线的集合;·逻辑总线:在配置空间中具有相同总线号码的一系列设备之间的逻辑连接;·逻辑设备:EGIO体系结构的元件,其在配置空间中对应于唯一的设备标识符;·存储器空间:EGIO体系结构的四个地址空间中的一个;·消息:具有消息空间类型的分组; N N pipeline link from the composition; • Link: Dual simplex (dual-simplex) communications path between the two components; two ports (one transmit and one receive) and their collection (s) Mutual Even a collection of pipelines; • Logical Bus: The logical range of devices with the same bus number in configuration space connection between; Logical equipment: element EGIO architecture, which in the configuration space corresponds to a unique device identifier; · memory space: four address space EGIO architecture a; · message: a message space type of packet;

·消息空间:EGIO体系结构的四个地址空间中的一个。 • Message space: four address space EGIO architecture in one. 如PCI中定义的特殊周期作为消息空间的子集而被包括在其中,并且因此提供了(多个)与老式设备的接口;·(多个)老式软件模型:初始化、发现、配置以及使用老式设备所需的(多个)软件模型(例如,在例如EGIO至老式桥中包含的PCI软件模型有助于与老式设备的交互);·物理层:EGIO体系结构层,其直接面对两个组件之间的通信介质;·端口:与组件相关联的接口,在该组件和EGIO链路之间;·接收器:通过链路接收分组信息的组件是接收器(有时称为目标);·请求:用于开始序列的分组被称为请求。 PCI special cycle as defined as a subset of message space is included therein, and thus provide a (multiple) interface with older equipment; · (s) old software model: initialization, discovery, configuration, and old-fashioned (s) required for the model of the device software (for example, such as PCI software model EGIO to the old bridge is included to help interact with the old equipment); • Physical Layer: EGIO architecture layer, which directly face the two a communication medium between the components; * port: an interface component associated with, between the component and the EGIO link; * Receiver: receiving packets of information over the link assembly is the receiver (sometimes referred to as the target); * Request: for packet start of the sequence is called the request. 请求包括一些操代码,并且在某些情况下,包括地址和长度、数据或其它信息;·请求器(requester):首先将序列引入到EGIO域的逻辑设备;·请求器ID:请求器的总线标识符(例如,总线号码)、设备标识符和功能标识符中的一个或多个的组合,其唯一的标识请求器。 Request includes some operation code and, in some cases, includes address and length, data or other information; · requester (requester): First, the sequence into the EGIO domain logic devices; · requester ID: requestor bus identifier (for example, bus number), device identifier and function identifiers of one or a combination of multiple, which uniquely identifies the requester. 在大多数情况下,EGIO桥或交换器(switch)将请求从一个接口转发到另一个接口而不修改请求器ID。 In most cases, EGIO bridge or switch (switch) forwards requests from one interface to another without modifying the requester ID. 来自除了EGIO总线的总线的桥通常应当存储请求器ID,以在为该请求产生一个完成时使用。 In addition to the bridge from the bus EGIO bus should typically store the requester ID, in order to produce for the request when a complete use.

·根复合体:包括主桥和一个或多个根端口的实体;·根端口:根复合体上的EGIO端口,其通过相关联的虚拟PCI-PCI桥来映射EGIO互连层次的一部分;·序列:与请求器执行单个逻辑传送相关联的零个或多个完成以及单个请求;·序列ID:请求器ID和标记的一个和多个的组合,其中所述组合唯一地标识作为公共序列一部分的完成和请求;·分裂事务(split transaction):含有初始事务(分裂请求)的单个逻辑传送,目标(完成器或桥)以分裂响应终止该事务,随后由完成器(或桥)开始一个或多个事务(分裂完成),以将读取数据(如果读取)或完成消息发送回请求器;·符号(symbol):作为8比特/10比特编码的结果而产生的10比特数值;·符号时间:在管线上放置符号所需的时间段;·标记:由请求器分配到给定序列以区分它和其它序列的号码一序列ID的一部分;·事务层分组(TLP):TLP是在事务层中产生以运送请求或完成的分组;·事务层:EGIO体系结构的最外层(最上层),其在事务级别进行操作(例如,读取、写入等等);·事务描述符:分组头部的元素,与地址、长度和类型一起描述事务的属性。 · Root complex: including the main bridge entity and one or more root ports; • Root port: root EGIO port complex on which to map part of the EGIO interconnect hierarchy through a virtual PCI-PCI bridge associated; · Sequence: transmission and zero or more to complete a single request associated with the implementation of a single logical requester; * Serial ID: request and combiner ID and mark one of the plurality, wherein the combination uniquely identifies a common sequence part completion and requests; · split transaction (split transaction): single logical containing the original transaction (split request) transfer target (complete or bridge) to terminate the transaction response division, then completed (or bridge) begins a or multiple transaction (split completed) in order to read the data (if read) or a completion message is sent back to the requester; * symbol (symbol): 10-bit values as an 8-bit / 10-bit encoding of the results produced; · symbols Time: Time symbol you want to place on the pipeline segment; • Tag: Assigned by the requester to a given sequence to distinguish between it and the other part of the sequence number of a sequence ID; • Transaction Layer Packet (TLP): TLP is in the business transporting produce to request or complete packet layer; • Transaction layer: the outermost EGIO architecture (uppermost layer), which carried out operations (for example, read, write, etc.) at the transaction level; · transaction descriptor: elements of the packet header, and the address, length, and type together with the description of the property transaction.

示例性电子装置以及EGIO体系结构图1提供了根据本发明示例性实施例的电子装置100的方框图,该电子装置100包括增强型通用输入/输出(EGIO)互连体系结构、协议及相关方法。 Exemplary electronic device and EGIO architecture Figure 1 provides a block diagram of an electronic device according to an exemplary embodiment of the present invention 100, the electronic device 100 includes enhanced general-purpose input / output (EGIO) interconnect architecture, protocol and related methods. 如所示,电子装置100被描述为包含多个电子元件,包括(多个)处理器102、根复合体(例如,包括主桥)104、交换器108以及端点110中的一个或多个,每个元件都如所示进行耦合。 As shown, the electronic device 100 is described as comprising a plurality of electronic components, including the processor (s) 102, a root complex (e.g., including host bridge) 104, switches 108 and end 110 of one or more, Each element is coupled as shown. 根据本发明的教导,至少根复合体104、(多个)交换器108以及端点110被赋予了EGIO通信接口106的一个或多个示例,以有助于本发明的实施例的一个或多个方面。 According to the teachings of the present invention, at least root complex 104, (s) 108 and switch 110 is given endpoint EGIO communication interface 106 of one or more examples, to facilitate an embodiment of the present invention, one or more aspect.

如所示,元件102、104、108和110中的每一个都经由EGIO接口106通过通信链路112可进行通信地耦合到至少一个其它元件,其中通信链路112支持一条或多条EGIO通信信道。 As shown, elements, and 110 each communicatively coupled 102,104,108 EGIO interface 106 via a communications link 112 can be performed by at least one other element, wherein the communication link 112 supports one or more EGIO communication channel . 根据一个示例性实现,在主电子装置的初始化事件期间或者在外围设备动态连接到电子装置(例如,热插拔设备)之后,建立了EGIO互连体系结构的操作参数。 According to an exemplary implementation later, in the main event during initialization or electronic device connected to the electronic device (for example, hot-swappable devices) in the peripheral dynamic, established operating parameters EGIO interconnection architecture. 如上面所介绍的,电子装置100被确定为代表多种传统和非传统计算系统、服务器、网络交换器、网络路由器、无线通信用户单元、无线通信电话基础设施元件、个人数字助理、机顶盒或任何电子装置中的任何一个或多个,所述任何电子装置将从通过这里描述的EGIO互连体系结构、通信协议或相关方法的至少一个子集的综合而产生的通信资源获益。 For example, the electronic device 100 described above is determined to be the representative of a variety of traditional and non-traditional computing systems, servers, network switches, network routers, wireless communication subscriber units, wireless communication telephony infrastructure elements, personal digital assistants, set-top boxes or any at least one communication resource sub-set of the benefits arising from the integrated electronic device in any one or more, EGIO interconnection architecture from the electronic device through any described herein, the communication protocol or related methods.

根据图1图示的示例性实现,电子装置100具有一个或多个处理器102。 According to an exemplary implementation illustrated in FIG. 1, the electronic device 100 having one or more processors 102. 如这里所使用的,(多个)处理器102控制电子装置100的功能性能力的一个或多个方面。 As used herein, processor (s) 102 controls the functional capabilities of an electronic device 100 or more aspects. 在这个方面,(多个)处理器102可以代表多种控制逻辑的任何一个,控制逻辑包括但不局限于微处理器、可编程逻辑器件(PLD)、可编程逻辑阵列(PLA)、专用集成电路(ASIC)、微控制器等等的一个或多个。 In this regard, processor (s) 102 may represent any one of a variety of control logic, the control logic including, but not limited to, a microprocessor, a programmable logic device (PLD), programmable logic array (PLA), application specific integrated Circuit (ASIC), a microcontroller, etc. one or more.

如上所述,根复合体104提供电子装置EGIO体系结构的一个或多个其它元件108、110与处理器102和/或处理器/存储器复合体之间的EGIO通信接口。 As described above, the root complex 104 provides an EGIO communications interface EGIO architecture of the electronic device or a plurality of processor 102 and other elements 108, 110 and / or the processor / memory complex between. 如这里所使用的,根复合体104指的是最靠近于主控制器、存储器控制器集线器、IO控制器集线器、上述的任何组合或芯片组/CPU元件的某种组合(即,处于计算系统环境)的EGIO层次的逻辑实体。 As used herein, refers to the root complex 104 is closest to the main controller, a memory controller hub, IO controller hub, any combination of the above or chipset / CPU elements of some combination of (i.e., in a computing system environment) EGIO hierarchy of logical entities. 在这方面,尽管在图1中被描述为单个单元,根复合体104可以被认为是具有多个物理组件的单个逻辑实体。 In this regard, although in FIG. 1 is described as a single unit, root complex 104 may be considered a single logical entity having a plurality of physical components.

根据图1所图示的示例性实现,根复合体104组装有一个或多个EGIO接口106以便于与其它外围设备进行通信,所述外围设备例如是(多个)交换器108、(多个)端点110以及(多个)老式桥114或116,尽管没有对老式桥114或116进行具体描述。 Illustrated in FIG. 1 according to an exemplary implementation, root complex 104 is assembled with one or more EGIO interface 106 to facilitate communication with other peripheral devices, for example, the peripheral device (s) switches 108, (s ) endpoint 110, and (s) old bridge 114 or 116, though not to the old bridge 114 or 116 will be specifically described. 根据一个示例性实现,每个EGIO接口106代表不同的EGIO层次域。 According to one example implementation, each EGIO interface 106 represents a different EGIO hierarchy domain. 在此方面,图1所图示的实现表示了具有三(3)个层次域的根复合体104。 In this regard, the realization illustrated in Figure 1 shows have three (3) level domain root complex 104. 应当知道,尽管所作的表述包括多个单独EGIO接口106,但是可以预期其它的实施例,其中单个接口106具有多个端口以适应和多个设备进行通信。 Be appreciated that, although the statements made EGIO interface 106 includes a plurality of individual, it is contemplated that other embodiments, wherein a single interface 106 having a plurality of ports to accommodate communication with multiple devices.

根据一个示例性实现,根复合体104负责识别EGIO体系结构的每个元件的通信需求(例如,虚拟信道需求、同步信道需求等等)。 According to one example implementation, root complex 104 is responsible for identifying the communication requirements of each element of the EGIO architecture (e.g., virtual channel requirements, synchronization channel requirements, etc.). 根据一个示例性实现,这样的通信需求在主装置100的初始化事件期间或它的任何元件的初始化事件期间(例如,热插拔事件)被传送到根复合体104。 According to an exemplary implementation, such communication requirements in the event the master device 100 during initialization or initialization event period (for example, hot-plug events) that any element 104 is transferred to the root complex. 在另一个实施例中,根复合体104询问这些元件以识别通信需求。 In another embodiment, root complex 104 identifying the communication needs to ask these elements. 一旦识别了这些通信参数,根复合体104就例如通过协商过程来为体系结构的每个元件建立EGIO通信设备的款项和条件。 Once you have identified these communication parameters, such as root complex 104 to establish funds and conditions EGIO communication device for each element architecture through the consultation process.

在这里公开的EGIO体系结构中,交换器有选择地将端点耦合到多个EGIO层次和/或域以及它们之间。 In the EGIO architecture disclosed herein, switches selectively coupling between a plurality of end-to-EGIO hierarchy and / or domains and them. 根据一个示例性实现,EGIO交换器具有至少一个上行流(upstream)端口(即、朝着根复合体104的方向)和至少一个下行流端口。 According to one example implementation, EGIO switch having at least one upstream (upstream) port (i.e., towards the direction of the root complex 104) and at least one downstream port. 根据一个实现,交换器108将最靠近根复合体的一个端口(即,接口的一个端口或接口106自身)作为上行流端口,而所有其它的端口是下行流端口。 According to one implementation, a switch 108 to the port closest to the root complex (i.e., an interface or port interface 106 itself) as the upstream port, while all other ports are downstream ports. 根据一个实现,交换器108对于配置软件(例如,老式配置软件)表现为PCI-PCI桥,并且使用PCI桥机制来对事务进行路由。 According to one implementation, switches 108 for configuration software (for example, the old configuration software) performance of PCI-PCI bridge, and use PCI bridge mechanisms for routing transactions.

在交换器108的上下文中,对等事务被定义为这样的事务,其中的接收端口和发送端口都是下行流端口。 In the context of the switch 108, the peer transaction is defined as a transaction in which the receive port and transmit ports are downstream ports. 根据一个实现,交换器108支持除了那些与从任何端口到任何其它端口的锁定事务序列相关联的事务层分组(TLP)之外的所有类型的事务层分组。 According to one implementation, switches 108 support in addition to those from any transaction layer packet to all types of other matters layer packet (TLP) port locked transaction sequence associated to any port outside. 在这方面,所有广播消息一般都会从交换器108上的接收端口被路由到它的所有其它端口。 In this regard, all broadcast messages generally are routed from the receiver port switch 108 to all its other ports. 不能被路由到端口的事务层分组一般会被交换器108确定为不支持的TLP。 The transaction layer packet can not be routed to the port switch 108 will generally be determined not to support TLP. 当将事务层分组(TLP)从接收端口传送到发送端口时,交换机108一般不修改它们,除非需要进行修改以适应发送端口(例如,耦合到老式桥114、116的发送端口)的不同协议需求。 When the transaction layer packet (TLP) is sent from the receiving port to the port, the switch 108 generally do not change them unless you need to be modified to accommodate the transmit port (for example, the old bridge is coupled to the transmit port 114, 116) of different protocol requirements .

应当意识到,交换器108代表其它设备工作,并且在这方面,它不会预先知道流量类型和模式。 It should be appreciated that the switch 108 to work on behalf of other devices, and in this regard, it will not know in advance the type and traffic patterns. 根据下面将要详细讨论的一个实现,本发明的流控制和数据完整性方面以每个链路(per-link)为基础而实现,而不是以端到端(end-to-end)为基础实现。 According to an implementation which will be discussed in detail, flow control and data integrity aspects of the invention with each link (per-link) based on realized rather than end (end-to-end) to the underlying implementation . 因此,根据这样的实现,交换器108参与用于流控制和数据完整性的协议。 Therefore, according to such an implementation, switches 108 participate in flow control and data integrity for the protocol. 为了参与流控制,交换器108为每个端口维持单独的流控制以提高交换器108的性能特性。 To participate in flow control, switch 108 for each port to maintain a separate flow control to improve the performance characteristics of the switch 108. 类似地,交换器108通过使用TLP检错机制检查进入交换器的每个TLP而以每个链路为基础来支持数据完整性过程,这在下面将详细描述。 Similarly, the switch 108 by using the TLP error detection mechanisms to check each TLP entering the switch on a per-link basis and supports data integrity processes, which will be described in detail below. 根据一个实现,交换器108的下行流端口允许形成新的EGIO层次域。 According to one implementation, switches 108 downstream ports allow the formation of new EGIO hierarchy domain.

继续参考图1,端点110被定义为具有00hex(十六进制00)(00h)类型配置空间头部的任何设备。 With continued reference to FIG. 1, the endpoint 110 is defined as any type of device having a configuration space header 00hex (hex 00) (00h). 端点设备110代表它自身或是代表截然不同的非EGIO设备,可以是EGIO语义事务的请求器或完成器。 Endpoint device itself or on behalf of 110 representatives of different non-EGIO device may be EGIO semantic transaction request or a complete unit. 这样的端点110示例包括但不局限于EGIO兼容(EGIO compliant)图形设备、EGIO兼容存储器控制器以及/或者实现了EGIO和诸如通用串行总线(USB)、以太网等某些其它接口之间的连接的设备。 110 endpoints such examples include, but are not limited to, EGIO-compliant (EGIO compliant) graphics device, EGIO-compliant memory controller and / or implement the EGIO and such as universal serial bus (USB), Ethernet and other some other interface between connected devices. 与下文详细讨论的老式桥114、116不同,担当非EGIO兼容设备的接口的端点110不会为这些非EGIO兼容设备提供完全软件支持。 The old bridge and discussed in detail below 114,116 different take on non-EGIO compliant device interface end 110 does not provide complete software support for these non-EGIO compliant devices. 虽然将主处理器复合体102连接到EGIO体系结构的设备是根复合体104,但是它可以与位于EGIO体系结构中的其它端点具有相同的设备类型,它们只是通过其相对于处理器复合体102的位置来加以区分。 Although the main processor complex 102 is connected to the device EGIO architecture is the root complex 104, it can communicate with other endpoints located EGIO architecture have the same type of equipment, they are only relative to the processor complex through 102 The position to be distinguished.

根据本发明的教导,端点110可以被概括为下列三个类别的一个或多个:(1)老式与EGIO兼容端点,(2)老式端点,以及(3)EGIO兼容端点,每个在EGIO体系结构中具有不同的操作规则。 According to the teachings of the present invention, the endpoint 110 can be summed up in one or more of the following three categories: (1) Vintage and EGIO-compliant endpoints, (2) legacy endpoints, and (3) EGIO-compliant endpoints, each in the EGIO system structures having different rules of operation.

如上所述,EGIO兼容端点110与老式端点(例如,118、120)不同,在于EGIO端点110将具有00h类型配置空间头部。 As described above, EGIO-compliant endpoints 110 and legacy endpoints (for example, 118, 120) is different from that EGIO end 110 will have 00h configuration space header type. 这些端点(110、118和120)的每个都作为完成器支持配置请求。 These endpoints (110, 118 and 120) are each configured as a complete support requests. 这些端点允许产生配置请求,并且可以被分类为老式端点或EGIO兼容端点,但是该分类需要遵守另外的规则。 These endpoints allows generation of configuration requests, and can be classified as old-fashioned or EGIO-compliant endpoint endpoint, but the classification need to comply with additional rules.

老式端点(例如,118、120)被允许作为完成器来支持IO请求并且被允许产生IO请求。 Legacy endpoints (for example, 118, 120) are permitted as a complete unit to support the IO request and be allowed to generate IO requests. 如果老式端点(118、120)的软件支持需求要求,则它被允许例如根据传统的PCI操作作为完成者产生锁定语义(locksemantics)。 If the legacy endpoints (118, 120) requires software support needs, such as it is allowed to produce as completers According to conventional PCI operation lock semantics (locksemantics). 老式端点(118、120)一般不发布锁定请求。 Legacy endpoints (118, 120) are generally not released the lock request.

EGIO兼容端点110一般不作为完成器来支持IO请求并且不产生IO请求。 EGIO-compliant endpoints 110 generally do not support IO request and does not generate IO requests as a complete unit. EGIO端点110不作为完成器来支持锁定请求,并且不作为请求器来产生锁定请求。 EGIO end 110 does not come as a complete device support lock requests, and not as a request, to produce the lock request.

EGIO至老式桥114、116是专用端点110,其包括用于老式设备(118、120)的基本软件支持例如完全软件支持,其中所述桥将所述老式设备连接到EGIO体系结构。 EGIO to the old bridge 114 is dedicated endpoints 110, which includes an old-fashioned device (118, 120) of the basic software support such as complete software support, wherein the bridge device to connect to the old EGIO architecture. 在这方面,EGIO-老式桥114、116一般具有一个上行流端口(也可以具有多个),并具有多个下行流端口(也可以只有一个)。 In this regard, EGIO- old bridge 114, 116 typically has a upstream port (you can have more than one), and having a plurality of downstream ports (you can have only one). 根据老式软件模型(例如,PCI软件模型)来支持锁定请求。 According to the old software model (for example, PCI software model) to support the lock request. EGIO-老式桥114、116的上行流端口应当以每个链路为基础来支持流控制并且遵守EGIO体系结构的流控制和数据完整性规则,这在下文将详细介绍。 EGIO- old bridge upstream port 114, should be the basis to support each link flow control and compliance with flow control and data integrity rules EGIO architecture, which will be hereinafter described in detail.

如这里所使用的,通信链路112被确定为代表多种通信介质中的任何一个,所述多种通信介质包括但不局限于铜线、光纤、(多条)无线通信信道、红外通信链路等等。 As used herein, communication link 112 is determined as a representative of a variety of communication media in any one of the plurality of communication media including, but not limited to, copper wire, fiber, (a plurality of) wireless communication channel, an infrared communication link so on the road. 根据一个示例性实现,EGIO链路112是差分串行线路对,一对中的每个都支持发送和接收通信,从而提供了对全双工通信能力的支持。 According to an exemplary implementation, EGIO link 112 is a differential serial line pairs, one for each support the sending and receiving communication, which provides support for full-duplex communications capabilities. 根据一个实现,链路提供具有初始(基本)操作频率为2.5Ghz的可变串行时钟频率。 According to one implementation, the link provides an initial (base) operating frequency of 2.5Ghz variable serial clock frequency. 每个方向的接口宽度可依x1、x2、x4、x8、x12、x16、x32物理管线而变。 Interface width in each direction may vary depending upon x1, x2, x4, x8, x12, x16, x32 physical line. 如上所述以及下面将要详细介绍的,EGIO链路112可以在设备之间支持多条虚拟信道,从而使用一条或多条虚拟信道在这些设备之间提供对同步流量的不间断通信的支持,所述多条虚拟信道例如是一条音频信道和一条视频信道。 As mentioned above and as will be described in detail, EGIO link 112 can support multiple virtual channels between devices, which use one or more virtual channels between these devices provide uninterrupted communications support for synchronous traffic, the said plurality of virtual channels, for example, an audio channel and a video channel.

示例性EGIO接口体系结构根据图2所图示的示例性实现,EGIO接口106可以表示为包括了事务层202、数据链路层204和物理层206的通信协议栈。 Exemplary EGIO Interface Architecture Figure 2 according to the illustrated exemplary implementation, EGIO interface 106 can be represented as including a transaction layer 202, data link layer 204 and physical layer 206 of the communication protocol stack. 如所示,物理链路层接口被描述为包括逻辑子块208和物理子块210,其中每个都将在进行下面详细讨论。 As shown, the physical link layer interface is described as comprising a logical sub-block 208 and physical sub-block 210, each of which will be discussed below in detail making.

事务层202根据本发明的教导,事务层202提供EGIO体系结构和设备核心之间的接口。 The transaction layer provides an interface 202 202 EGIO architecture and equipment between the core of the teachings, the transaction layer of the present invention. 在这方面,事务层202的主要职责是为主设备(或代理)中的一个或多个逻辑设备装配和拆解分组(即,事务层分组或TLP)。 In this regard, the transaction layer 202 primary responsibility is the main device (or proxy) in one or more logical devices packet assembly and disassembly (ie, transaction layer packet or TLP).

地址空间、事务类型和用途事务形成了在发起代理和目标代理之间的信息传送的基础。 Address space, transaction types and transaction forms the basis of use between the initiator and target proxy proxy information transfer. 根据一个示例性实施例,在创新的EGIO体系结构中定义了四个地址空间,包括例如配置地址空间、存储器地址空间、输入/输出地址空间以及消息地址空间,每个都具有自己唯一的既定用途(例如见图7,下面进行了详细的说明)。 According to an exemplary embodiment, the innovative EGIO architecture, four address spaces are defined, including for example, the configuration address space, the memory address space, an input / output address space and a message address space, each with its own unique intended usage (e.g. see FIG. 7, a detailed description below).

存储器空间(706)事务包括读取请求和写入请求中的一个或多个,以将数据发送到存储器映射位置或从该位置取出数据。 Memory space (706) transactions include read requests and write requests to one or more of, to send data to the memory map or removing the data from the position. 存储器空间事务可以使用两种不同的地址格式,例如短地址格式(例如,32比特地址)或长地址格式(例如,64比特的长度)。 Memory space transactions may use two different address formats, such as short address format (for example, 32-bit address) or long address format (for example, 64 bits in length). 根据一个示例性实施例,EGIO体系结构使用锁定协议语义(即,代理可以锁定对所修改的存储器空间的访问)来提供传统的读取、修改和写入序列。 According to an exemplary embodiment, EGIO architecture uses the lock protocol semantics (ie, the agent can lock access to modified memory space) to provide traditional read, modify and write sequence. 更具体地说,根据特定设备规则(桥、交换器、端点、老式桥),允许对下行流锁定的支持。 More specifically, according to the particular device rules (bridge, switch, endpoint, the old bridge), allowing for downstream lock support. 如上所述,支持该锁定语义以帮助老式设备。 As described above, in order to help support the locking semantics old equipment.

IO空间(704)事务用于访问IO地址空间(例如,16比特IO地址空间)中的输入/输出映射存储器寄存器。 IO space (704) transactions for accessing the IO address space (for example, 16-bit IO address space) input / output mapped memory registers. 诸如英特尔体系结构处理器以及其它处理器的某些处理器102通过处理器的指令集而包括IO空间定义。 Such as Intel Architecture processors and other processors some processor 102 comprises a processor instruction set and IO space definition. 因此,IO空间事务包括读取请求和写入请求以将数据传送至IO映射位置或从该位置取出数据。 Thus, IO space transactions include read requests and write requests to transfer data to the IO mapped location or remove data from that location.

配置空间(702)事务用于访问EGIO设备的配置空间。 Configuration space (702) transactions EGIO devices used to access the configuration space. 配置空间的事务包括读取请求和写入请求。 Configuration space transactions include read requests and write requests. 由于如此多的传统处理器一般不含有本地配置空间,所以通过一种机制来映射该空间,所述机制即是与传统PCI配置空间访问机制(例如,使用基于CFC/CFC8的PCI配置机制#1)相兼容的软件。 Because so many of the traditional processors generally do not contain local configuration space, by a mechanism to map the space, the mechanism that is the traditional PCI configuration space access mechanisms (for example, based CFC / CFC8 the PCI configuration mechanism # 1 ) compatible software. 或者,也可以使用存储器别名机制来访问配置空间。 Alternatively, you can use the memory alias mechanism to access the configuration space.

消息空间(708)事务(或简称为消息)被定义为支持通过(多个)接口106而在EGIO代理之间进行带内通信。 Message space (708) transactions (or simply messages) are defined to support through (multiple) interface 106 between EGIO agents band communication. 由于传统的处理器不包括对本地消息空间的支持,所以这是通过EGIO代理在接口106中实现的。 Because conventional processor does not include support for local news space, so this is by EGIO agent interface 106 implemented. 根据一个示例性实现,诸如中断和电源管理请求的传统“边带(side-band)”信号作为消息而被实现以减少所需的用来支持这些老式信号的引脚数目。 According to an exemplary implementation, such as interrupts and power management requests traditional "sideband (side-band)" is realized as a message signal to reduce the required number of those older signals to support pins. 一些处理器以及PCI总线包括“特殊周期”的概念,其也被映射到EGIO接口106中的消息。 Some processors, and the PCI bus include the concept of "special cycles", which is also mapped to the EGIO interface 106 messages. 根据一个实施例,消息通常分为两类:标准消息和厂商定义消息。 According to one embodiment, messages are typically divided into two categories: standard messages and vendor-defined messages.

根据所图示的示例性实施例,标准消息包括通用消息组和系统管理消息组。 According to an exemplary embodiment illustrated, the standard message including universal message group and system management message group. 通用消息可以是单一目的地消息或广播/组播消息。 General message may be a single destination message or a broadcast / multicast messages. 系统管理消息组可以包括中断控制消息、电源管理消息、排序控制原语(primitive)和错误信令中的一个或多个,它们的例子将在下文介绍。 System management message group may include interrupt control messages, power management messages, ordering control primitives (primitive) and error signaling one or more examples of which are described below.

根据一个示例性实现,通用消息包括支持锁定事务的消息。 According to an exemplary implementation, including support for locking affairs General news news. 根据该示例性实现,引入了UNLOCK(解锁)消息,其中交换器(例如,108)一般会通过可能参与锁定事务的任何端口来运送UNLOCK消息。 According to this exemplary implementation, the introduction of UNLOCK (unlock) messages, wherein the switching device (for example, 108) are generally locked by any port may be involved in a transaction to transport UNLOCK message. 在没有被锁定的时候接收到UNLOCK消息的端点设备(例如,110、118、120)将忽略该消息。 Without being locked when the received UNLOCK message endpoint devices (for example, 110,118,120) will ignore the message. 否则,将在接收到UNLOCK消息之后解锁锁定设备。 Otherwise, it will unlock a locked device after receiving the UNLOCK message.

根据一个示例性实现,系统管理消息组包括用于排序和/或同步的专用消息。 According to an exemplary implementation, the system management message group includes for sorting and / or special message synchronization. 一个这样的消息是FENCE(防护)消息,用于在由EGIO体系结构的接收元件产生的事务上施加严格的排序规则。 One such message is a FENCE (protection) message, for applying strict ordering rules on transactions by the receiving element EGIO architecture generated. 根据一个实现,只是诸如端点的网络元件的一个精选子集对该FENCE消息作出反应。 According to one implementation, only a select subset of endpoints such as network elements to respond to the FENCE message. 除了前述的内容,例如通过使用下文讨论的尾部(tailer)错误转发,这里还预见了用于指示可校正错误、不可校正错误和致命错误的消息。 In addition to the foregoing contents, e.g., by use of the tail discussed below (tailer) error forwarding, there is also foreseen for indicating a correctable error, uncorrectable error, and fatal error message.

根据上文所介绍的本发明的一个方面,系统管理消息组使用带内消息提供中断信令。 According to one aspect of the present invention described above, the system management message group provides interrupts using in-band signaling messages. 根据一个实现,引入了ASSERT_INTx/DEASSERT_INTx消息对,其中断言(assert)中断消息的发布通过根复合体104被发送到处理器复合体。 According to one implementation, the introduction of ASSERT_INTx / DEASSERT_INTx news, including the assertion (assert) interrupt message released by the root complex 104 is sent to the processor complex. 根据所图示的示例性实现,ASSERT_INTx/DEASSERT_INTx消息对的使用规则反映了PCI规范中的PCI INTx#信号的消息的使用规则,如上所述。 According to the illustrated example implementation, usage rules ASSERT_INTx / DEASSERT_INTx news reflects the PCI specification using rules PCI INTx # signal of the message, as described above. 对于来自任何一个设备的Assert_INTx的每次发送,通常都有对应的Deassert_INTx的发送。 For Assert_INTx from any one of the devices of each transmission, usually we have a corresponding Deassert_INTx transmission. 对于特定'x'(A、B、C或D),一般在发送Deassert_INTx之前只发送一次Assert_INTx。 For a particular 'x' (A, B, C or D), typically sent only once before transmission Deassert_INTx Assert_INTx. 交换器一般会将Assert_INTx/Deassart_INTx消息路由到根复合体104,其中根复合体一般会跟踪Assert_INTx/Deassart_INTx消息以产生虚拟中断信号,并且将这些信号映射到系统中断资源。 Switch will normally Assert_INTx / Deassart_INTx message is routed to the root complex 104, which typically track root complex Assert_INTx / Deassart_INTx message to generate virtual interrupt signals and map these signals to system interrupt resources.

除了通用和系统管理消息组之外,EGIO体系结构建立了标准框架结构,其中核心逻辑(例如芯片组)厂商可以定义它们自己的厂商定义消息以迎合它们的平台的特定操作需求。 In addition to general and system management message group, EGIO architecture to establish a standard framework, in which the core logic (eg, chipset) vendors can define their own vendor-defined message to meet the specific operational requirements of their platforms. 该框架结构是通过公共消息头部而建立的,在所述头部中厂商定义消息的编码被规定为“预留”。 The frame structure is established through common message header in the header coding vendor-defined message is defined as "reserved."

事务描述符事务描述符是用于将事务信息从起点运送到服务点并送回的机制。 Transaction descriptors transaction descriptor is a mechanism for delivery of transaction information from the start point and returned to service. 它提供可扩展装置用于提供可以支持新类型的新兴应用的一般互连解决方案。 It provides scalable general means for providing interconnect solutions to support new types of emerging applications. 在这方面,事务描述符支持系统中的事务的标识、缺省事务排序的修改,以及使用虚拟信道ID机制关联事务与虚拟信道。 In this regard, modify transaction descriptors support system identifies the transaction, the default transaction ordering, and the use of virtual channel ID mechanism associated with the transaction with virtual channels. 参考图3,示出了事务描述符的示图。 Referring to Figure 3, there is shown a diagram of transaction descriptors.

参考图3,根据本发明的教导示出了包括示例性事务描述符的数据报的示图。 Referring to Figure 3, according to the teachings of the present invention is shown an exemplary transaction descriptors include datagrams diagram. 根据本发明的教导,示出的事务描述符300包括全局标识符字段302、属性字段304和虚拟信道标识符字段306。 According to the teachings of the present invention, showing the transaction descriptor 300 includes a global identifier field 302, attribute fields 304 and virtual channel identifier field 306. 在所图示的示例性实现中,全局标识符字段302被描述为包括本地事务标识符字段308和源标识符字段310。 In the illustrated exemplary implementation, the global identifier field 302 is described as comprising a local transaction identifier field 308 and a source identifier field 310.

·全局事务标识符302如这里所使用的,全局事务标识符对所有待处理的请求都是唯一的。 · A global transaction identifier 302] As used herein, the global transaction identifier for all pending requests are unique. 根据图3所图示的示例性实现,全局事务标识符302包括两个子字段:本地事务标识符字段308和源标识符字段310。 According to the illustrated exemplary implementation of FIG. 3, the global transaction identifier 302 consists of two sub-fields: the local transaction identifier field 308 and a source identifier field 310. 根据一个实现,本地事务标识符字段308是由每个请求器产生的8比特字段,并且对于需要该请求器的完成的所有待处理请求它是唯一的。 According to one implementation, the local transaction identifier field 308 is an 8-bit field produced by each requestor, the requestor and the need for all pending completion of the request it is unique. 源标识符唯一地标识EGIO层次中的EGIO代理。 Source identifier uniquely identifies the EGIO hierarchy EGIO agents. 因此,本地事务标识符字段和源ID一起提供了在层次域中的事务的全局标识。 Therefore, local transaction identifier field and the source ID provides a global level domains identified in the transaction together.

根据一个实现,本地事务标识符308允许来自单个请求源的请求/完成不依顺序(遵守下面详细讨论的排序规则)而被操作。 According to one implementation, the local transaction identifier 308 allows requests from a single source of the request / completion of non-compliance order (compliance collation discussed in detail below) is operating. 例如,读取请求源可以产生读取A1和A2。 For example, the read request source can produce read A1 and A2. 处理这些读取请求的目的地代理会首先返回请求A2事务ID的完成,并且随后返回A1的完成。 Processing these read requests destination agent first return to complete the request A2 transaction ID, and then returned to A1 is completed. 在完成分组头部中,本地事务ID信息将标识哪个事务将被完成。 Upon completion packet header, local transaction ID information will identify which transaction will be completed. 这种机制对于使用分布式存储器系统的装置尤为重要,因为它可以更有效的方式来操作读取请求。 This mechanism is particularly important for the use of a distributed memory system means, because it can be more efficient way to operate the read request. 应当注意,对这种不依顺序读取完成的支持假定了发布读取请求的设备将确保完成的缓冲器空间的预先分配。 It should be noted that this non-compliance in order to read the publication assume complete support device read requests will ensure the completion of the pre-allocated buffer space. 如上所述,只要EGIO交换机108不是端点(即,仅仅传送完成请求到适当的端点),它们就不需要预留缓冲器空间。 As described above, as long as EGIO switches 108 are not end points (i.e., only complete transfer request to the appropriate endpoint), they do not need to reserve buffer space.

单个读取请求可以产生多个完成。 Single read request can generate multiple completions. 属于单个读取请求的完成可以相互不依顺序的返回。 Completion of belonging to a single read request can return mutual non-compliance order. 这通过在完成分组头部(即,完成头部)中提供对应于部分完成的初始请求的地址偏移来只支持。 This is accomplished by providing complete packet header portion corresponding to the initial request to complete the address offset only support (ie, complete head).

根据一个示例性实现,源标识符字段310包含16比特值,其对每个逻辑EGIO设备是唯一的。 According to an exemplary implementation, the source identifier field 310 contains a 16-bit value, which for each logical EGIO device is unique. 应当注意单个EGIO设备可以包括多个逻辑设备。 It is noted that a single EGIO device may comprise a plurality of logical devices. 在系统配置期间以对标准PCI总线枚举机制透明的方式分配源ID值。 In the standard PCI bus enumeration mechanism in a transparent manner assignment source ID values during system configuration. EGIO设备使用例如在对那些设备的初始配置访问期间可用的总线号码信息以及用于表示例如设备号码和流号码的内部可用信息,在内部自动地建立源ID。 EGIO device using, for example during the initial configuration of the access to those devices available bus number information indicating the number and flow of internal devices such as the number of available information, the source ID is automatically established internally. 根据一个实现,该总线号码信息是在EGIO配置周期期间使用与PCI配置所使用的相类似的机制而产生的。 According to one implementation, the bus number information is to use a mechanism similar to the PCI configuration used during EGIO configuration cycles generated. 根据一个实现,总线号码由PCI初始化机制分配并由每个设备捕获。 According to one implementation, the bus number assigned by a PCI initialization mechanism captured by each device. 在热插拔和热交换设备的情况下,这些设备将需要在每个配置周期访问上重新捕获该总线号码信息以能够对热插拔控制器(例如,标准热插拔控制器(SHPC))软件栈透明。 In the case of hot-swap and hot-swap devices, these devices will need to re-capture this bus number information on every configuration cycle access to be able to hot-swap controller (for example, the standard hot-swap controller (SHPC)) software stack transparent.

根据EGIO体系结构的一个实现,物理组件可以包含一个或多个逻辑设备(或代理)。 According to one implementation of the EGIO architecture, a physical component may comprise one or more logical devices (or proxy). 每个逻辑设备被设计成响应于指定到其特定设备号码的配置周期,即,在逻辑设备中加入了设备号码的概念。 Each logical device is designed to respond to a particular device number assigned to its configuration cycle, that is, in the logic device by adding the concept of device numbers. 根据一个实现,在单个物理组件中允许多达十六个逻辑设备。 According to one implementation, a single physical component allows up to sixteen logical devices. 每个这样的逻辑设备可以包括一个或多个流化(streaming)引擎,例如最多16个。 Each such logical devices may comprise one or more fluidized (streaming) engine, such as up to 16. 因此,单个物理组件可以包括多达256个流化引擎。 Thus, a single physical component may comprise up to 256 streaming engine.

由不同源标识符标记的事务属于不同的逻辑EGIO输入/输出(IO)源,并且从而从排序的方面来看可以相互完全独立地操作这些事务。 Marked by a different source identifiers belong to different logical EGIO transaction input / output (IO) source, and thus can operate completely independent from each other in terms of these transactions the sort of view. 对于三方、对等事务的情况,如果需要可以使用防护排序控制原语来强制排序。 In the case of the three parties on other matters, and if necessary use protective ordering control primitives to enforce the order.

如这里所使用的,事务描述符300的全局事务标识符字段302遵守下列规则的至少一个子集:(a)每个需要完成的请求用全局事务ID(GTID)来标记;(b)由代理发起的所有待处理的需要完成的请求一般应当分配唯一的GTID;(c)不需要完成的请求不使用GTID的本地事务ID字段308,并且本地事务ID字段被认为是预留的;(d)目标不需要以任何方式来修改请求GTID,而只是为所有与请求相关联的完成在完成分组的头部中回应它,其中发起者使用GTID将(多个)完成与原始请求相匹配。 As used herein, the transaction descriptor global transaction identifier field 300, 302 with the following rules at least a subset of: (a) Each request needs to be done with the global transaction ID (GTID) to mark; (b) by the agent need to complete all pending requests to initiate generally be assigned a unique GTID; (c) does not require the completion of the request does not use GTID local transaction ID field 308, and the local transaction ID field is considered to be reserved; (d) Target does not need in any way to modify the request GTID, and just for all completed responses associated with the request to complete it in the packet header, where the initiator will use GTID (s) to complete the match with the original request.

·属性字段304如这里所使用的,属性字段304指明了事务的特性和关系。 · Attribute field 304] As used herein, the property field 304 indicates the characteristics and relationship issues. 在这方面,属性字段304被用于提供允许修改事务的缺省操作的额外信息。 In this regard, the property field 304 is provided to allow the transaction to modify the default action for additional information. 这些修改可以应用于在系统中操作事务的不同方面,例如排序、硬件一致性(coherency)管理(例如探听(snoop)属性)和优先级。 These modifications can be applied to the operation of business at different aspects of the system, such as sorting, hardware consistency (coherency) management (such as Snoop (snoop) property) and priority. 一种示例性格式以子字段312-318来表示属性字段304。 An exemplary format subfield 312-318 to indicate an attribute field 304.

如所示,属性字段304包括优先级子字段312。 As shown, the attribute field 304 includes a priority sub-field 312. 优先级子字段可以由发起者修改以为事务分配优先级。 Priority sub-fields can be modified by the originator that matters assigned priorities. 在一个示例性实现中,事务或代理的服务特性的等级或质量可以在优先级子字段312中实现,从而影响其它系统元件进行的处理。 In one exemplary implementation, the level or quality of service characteristics of a transaction or a proxy may be implemented in the priority sub-field 312, thereby affecting the processing of other system elements.

预留属性字段314为将来或厂商定义用途而被预留。 Reserved attribute field 314 for future use or vendor-defined and reserved. 通过使用预留属性字段可以实现使用优先级或安全属性的用途模型。 By using the reserved attribute field to achieve the intended use model precedence or security attributes.

排序属性字段316被用于提供用来传达排序类型的可选信息,所述信息可以修改同一排序平面(plane)(其中排序平面包括由具有对应的源ID的IO设备和主处理器(102)发起的流量)内的缺省排序规则。 Sort attribute field 316 is used to provide optional information to convey the sort type, the same sort of information you can modify the plane (plane) (where the ordering plane includes having the corresponding source ID of the IO device and the main processor (102) The default collation initiated traffic) inside. 根据一个示例性实现,排序属性'0'表示将应用缺省的排序规则,而排序规则'1'表示松散(relaxed)排序,其中在同一方向上写入可以超过写入,并且在同一方向上读取完成可以超过写入。 According to an exemplary implementation, sorting Properties '0' will apply the default collation, and collation '1' indicates loose (relaxed) sort, which is written in the same direction can be written over and in the same direction read completion can be written over. 使用松散排序语义的设备主要用于以缺省排序来为读取/写入状态信息移动数据和事务。 Use relaxed ordering semantics equipment is mainly used in the default sort to read / write status information of the mobile data and transactions.

探听属性字段318被用于提供用来传达高速缓存一致性管理的类型的可选信息,所述信息可以修改同一排序平面内的缺省高速缓存一致性管理规则,其中排序平面包括由具有对应的源ID的IO设备和主处理器(102)发起的流量。 Snoop attribute field 318 is used to provide information to convey optional cache coherency management types, the information may modify default cache coherency management rules within the same ordering plane, which includes sorting plane has a corresponding Source ID IO device and the main processor (102) sponsored traffic. 根据一个示例性实现,探听属性字段318值'0'对应于缺省高速缓存一致性管理方案,其中探听事务以增强硬件级别的高速缓存一致性。 According to an exemplary implementation, the snoop attribute field 318 value '0' corresponds to a default cache coherency management scheme, which snoop transactions to enhance the hardware level cache coherency. 另一方面,探听属性字段318中的值'1'中止缺省高速缓存一致性管理方案,并且事务没有被探听。 On the other hand, snoop attribute field 318 value of '1' to suspend the default cache coherency management scheme, and the transaction was not snooping. 相反,所访问的数据或者是非可高速缓存的(non-cacheable),或者其一致性由软件来管理。 On the contrary, the accessed data or non-cacheable (non-cacheable), or by the software to manage its consistency.

·虚拟信道ID字段306如这里所使用的,虚拟信道ID字段306标识与事务相关联的独立虚拟信道。 · Virtual channel ID field 306] As used herein, the virtual channel ID field 306 identifies an independent virtual channel associated with the transaction. 根据一个实施例,虚拟信道标识符(VCID)是4比特字段,其允许以每个事务为基础来标识多达16个虚拟信道(VC)。 According to one embodiment, the virtual channel identifier (VCID) is a four-bit field, which allows per transaction basis to identify up to 16 virtual channels (VC). 下面的表I中提供了VCID定义的一个示例: Table I below provides an example VCID definition:

表I:虚拟信道ID编码虚拟信道根据本发明的一个方面,EGIO接口106的事务层202支持在EGIO通信链路112的带宽内建立和使用(多条)虚拟信道。 Table I: virtual channel ID encoder 202 supports virtual channel 112 in EGIO communication link bandwidth set up and use (s) virtual channel, according to one aspect of the present invention, EGIO interfaces transaction layer 106. 如上所述的本发明的虚拟信道(VC)方面被用于基于将要通过信道传输的内容的所需的独立性而在单个物理EGIO链路112中定义单独的逻辑通信接口。 Virtual channel (VC) aspect of the invention as described above is used will be defined based on separate logical communication interfaces within a single physical EGIO link 112 by the independence required content channel transmission. 在这方面,虚拟信道可以基于一个或多个特性来建立,例如带宽需求、服务等级、服务类型(例如系统服务信道)等等。 In this regard, virtual channels may be based on one or more characteristics of the establishment, such as bandwidth requirements, service level, service type (e.g., system service channel) and the like.

(多条)虚拟信道和流量(或事务)等级标识符的组合被提供以支持某些等级的应用支持的有区别的服务和服务质量(QoS)。 (S) a combination of virtual channel and flow (or transaction) level identifier is provided in order to support some level of application support services and quality differentiated service (QoS). 如这里所使用的,流量(或事务)等级是事务层分组标签,其通过EGIO组织结构而未经修改端到端地进行传输。 As used herein, the flow (or transactions) rating is a transaction layer packet label, its organizational structure through EGIO transmitted unaltered end to end. 在每个服务点(例如,交换器、根复合体等等)处,服务点使用流量等级标签来应用适当的服务策略。 At each point of service (for example, switches, root complex, etc.) at the point of service using a traffic class labels to apply the appropriate service strategy. 在这方面,单独的VC被用于映射流量,所述流量将从不同操作策略和服务优先级获益。 In this regard, a separate VC is used to map the flow rate, the flow rate different from the operating strategy and service priority benefit. 例如,就确保T时间段内所传输的数据量X而言,需要确定性服务质量的流量可以被映射到同步(或时间协同)虚拟信道。 For example, to ensure that the amount of data transmitted time period T X, the need deterministic quality of service may be mapped to a synchronous flow (or time coordinated) virtual channel. 映射到不同虚拟信道的事务相互之间可以没有任何排序需求。 Mapped to different virtual channels between transactions mutually without any sort of demand. 即,虚拟信道作为单独逻辑接口来操作,其具有不同的流控制规则和属性。 That is, the virtual channel to operate as a single logical interface that has a different flow control rules and attributes.

根据本发明的一个示例性实现,EGIO兼容元件的每个EGIO通信端口(输入或输出)包括端口能力数据结构(未具体描述)。 According to an exemplary implementation of the present invention, EGIO compatible with each EGIO communication port (input or output) port capacity element comprises a data structure (not specifically illustrated). 包括(a)由端口支持的虚拟信道的数目,(b)与每个虚拟信道相关联的流量等级,(c)端口VC状态寄存器,(d)端口VC控制寄存器,以及(e)与这样的虚拟信道相关联的仲裁方案中的一个或多个的关于端口能力的信息保持在端口能力数据结构中。 Including (a) by the number of ports supported channels of virtual, (b) with each virtual channel associated with the traffic class, (c) port VC status register, (d) port VC control registers, and (e) of this virtual channel associated with the arbitration scheme of one or more of the information about the port capability is maintained at a port capability data structure. 根据一个示例性实现,以每个链路、每个VC为基础在耦合的元件之间协商通信操作参数和关联的端口能力参数。 According to an exemplary implementation, to each link, each VC port basis for the ability parameter in the communication negotiation between the coupling elements and the associated operating parameters.

对于由主处理器102发起的流量,虚拟信道可以要求基于缺省排序机制规则的排序控制,或者可以完全不依顺序地操作流量。 Initiated by the main processor 102 for traffic, the virtual channel can request the default sort mechanism sorting rule-based control, or it can operate completely failing to flow sequentially. 根据一个示例性实现,VC包含下列两种类型的流量:通用IO流量和同步流量。 According to an exemplary implementation, VC contains the following two types of traffic: general purpose IO traffic and synchronous traffic. 即,根据该示例性实现,描述了两类虚拟信道:(1)通用IO虚拟信道,和(2)同步虚拟信道。 That is, according to this exemplary implementation, described two types of virtual channels: (1) general purpose IO virtual channels, and (2) synchronous virtual channels.

如这里所使用的,事务层202为组件主动支持的一个或多个虚拟信道的每个保持独立流控制。 As used herein, transaction layer 202 is a component active support of one or more virtual channels each remain independent flow control. 如这里所使用的,所有的EGIO兼容组件一般都会支持缺省通用IO类型虚拟信道,例如虚拟信道0,它的服务等级是“尽最大努力(best effort)”,其中在这一类型的不同虚拟信道之间不需要排序关系。 As used herein, all EGIO-compliant components usually support the default general IO type virtual channel, for example, virtual channel 0, its service level is "best effort (best effort)", in which different virtual in this type of It does not require sorting between channels. 缺省地,VC0被用于通用IO流量,而VC1或更高(VC1-VC7)被分配用于操作同步流量。 By default, VC0 be used for general purpose IO traffic, and VC1 or higher (VC1-VC7) are allocated for operating synchronous traffic. 在另一个实现中,任何虚拟信道都可以被分配用于操作任何流量类型。 In another implementation, any virtual channel can be assigned to operate any type of traffic. 参考图4,示出了包括多条独立管理的虚拟信道的EGIO链路的概念示图。 Referring to Figure 4, shows a conceptual diagram includes a plurality of virtual channel independently managed the EGIO link.

参考图4,根据本发明的一个方面,示出了包括多条虚拟信道(VC)的示例性EGIO链路112的示图。 Referring to Figure 4, according to one aspect of the present invention, it is shown comprising a plurality of virtual channels (VC) exemplary EGIO link 112 shown in FIG. 根据图4所图示的示例性实现,示出的EGIO链路112包括在EGIO接口106之间创建的多条虚拟信道402、404。 According to the illustrated exemplary implementation of FIG. 4, EGIO link 112 is shown comprising a plurality of virtual channels 106 created between EGIO interfaces 402, 404. 根据一个示例性实现,对于虚拟信道402,示出了来自多个源406A...N的流量,这些流量至少由它们的源ID来区分。 According to an exemplary implementation, the virtual channel 402, shows a plurality of sources 406A ... N traffic from these flows by at least their source ID to distinguish. 如所示,建立了虚拟信道402,并且在来自不同源(例如,代理、接口等)的事务之间没有排序需求。 As shown, the establishment of a virtual channel 402, and between transactions from different sources (for example, agents, interfaces, etc.) are not sorted needs.

类似地,示出的虚拟信道404包括来自多个源多个事务408A...N的流量,其中每个事务由至少一个源ID指示。 Similarly, the illustrated virtual channel 404 includes flow 408A ... N, where each transaction by at least one source ID indicating multiple transactions from multiple sources. 根据图示的示例,来自源ID0 406A的事务被严格排序,除非由事务头部的属性字段304所修改,而来自源408N的事务没有这样的排序规则。 According to the illustrated example, from the source ID0 406A transactions are strongly ordered unless the transaction attribute field 304 to modify the header, and from the source 408N of affairs no such collation.

同步信道如上所述,建立同步信道以在电子装置100的EGIO体系结构中的请求器代理和(多个)完成器代理之间传输对时间敏感的内容(例如,多媒体内容流)。 Synchronization channel as described above, in order to establish a synchronization channel in EGIO architecture of the electronic device 100 requests proxy, and (s) to complete the transfer agent between time-sensitive content (for example, multimedia content streaming). 根据一个示例性实现,在EGIO体系结构之间存在两个不同的同步通信范例,例如,端点到根复合体模型以及对等(或端点到端点)通信模型。 According to an exemplary implementation, there are two different examples of synchronous communication between EGIO architecture, e.g., end-to-root complex model and a peer (or endpoint to endpoint) communication model.

在端点到根复合体模型中,主要的同步流量是对根复合体104的存储器读取和写入请求以及来自根复合体104的读取完成。 In the end-to-root complex model, the main flow is synchronized root complex 104 of memory read and write requests and read from the root complex 104 is completed. 在对等模型中,同步流量局限为单播(unicast)、仅压入(push-only)事务(例如,诸如存储器写入的公布事务或消息)。 In the peer model, the synchronous traffic limited to a unicast (unicast), only pushed (push-only) services (for example, the publication of a transaction such as memory write or message). 仅压入事务可以在单个主域中或是多个主域中。 You can only push into the transaction, or multiple primary domain in a single master domain.

为了支持具有保证带宽和确定性服务延迟的同步数据传输,在请求器/完成器对和EGIO通信组织结构之间建立了同步“协定”。 To support synchronous data transmission services with guaranteed bandwidth and deterministic latency, in a requester / finisher EGIO communication between organizational structure and the establishment of Synchronization "agreement." 根据一个实施例,“协定”将执行资源预留和流量调整以防止虚拟信道上的拥塞和过度预约。 According to one embodiment, the "agreement" to perform resource reservation and flow adjustment in order to prevent congestion on the virtual channel and excessive appointments.

参考图5,示出了用于在EGIO体系结构中建立并管理同步通信信道的示例性方法。 Referring to Figure 5, there is shown an exemplary method for establishing and managing a synchronous communication channel in EGIO architecture. 根据图5所图示的示例性实施例,方法以方框502开始,其中识别了EGIO组织结构的一个或多个元件(即、根复合体104、交换器108、端点110、链路112、桥114等等)的通信能力。 According to Figure 5 illustrates an exemplary embodiment, the method begins with block 502, wherein identifying one or more elements of EGIO structure (i.e., root complex 104, switch 108, endpoint 110, link 112, bridge 114, etc.) of communication capabilities.

根据一个示例性实现,EGIO组织结构的至少一个子集的通信能力对根复合体104的带宽管理器公开,该带宽管理器管理EGIO体系结构中的同步通信资源的地址分配。 According to an exemplary implementation, the communication capacity of at least a subset of EGIO organizational structure of root complex 104 Bandwidth Manager open, the address of the Bandwidth Manager EGIO architecture synchronous communication resource allocation. 在元件的初始化期间发生元件的通信能力的公开,例如在主电子装置100启动的时候,或者在EGIO兼容设备热插拔到主电子装置的时候。 Open communication capabilities such as the main element of the electronic device 100 is started, or hot-swap EGIO compliant devices to the main electronic device when occurred during initialization element in. 根据一个实施例,公开的信息(例如来自EGIO代理106中的数据结构)包括端口标识、端口地址分配、(多个)虚拟信道分配、带宽能力等等中的一个或多个。 According to one embodiment, the disclosed information (such as from EGIO agent 106 in the data structure) includes port identification, port address assignment (s) virtual channel allocation, bandwidth capabilities, and so the implementation of one or more. 该信息保存在可由带宽管理器访问的数据结构中以用于生成同步协定,这在下文将详细描述。 This information may be stored in the Bandwidth Manager to access the data structure for generating a synchronization protocol, which will be described in detail hereinafter.

在电子装置100的常规操作过程期间,可能需要或期望在装置100中的两个(或多个)代理之间建立同步通信信道。 During normal operation of the electronic device 100, it may be necessary or desirable in both device 100 (or more) to establish synchronous communication channel between the agents. 在这种情况下,在方框504中,根复合体104的带宽管理器从(或代表)请求器/完成器对接收对EGIO组织结构中的同步通信资源的请求。 In this case, at block 504, the root complex from 104 Bandwidth Manager (or representative) requestor / finisher receives a request for the organizational structure of the EGIO synchronous communication resources. 如这里所使用的,请求包括诸如带宽和服务延迟需求的期望通信资源的指示。 As used herein, request indication including bandwidth and service latency requirements such as a desired communication resources.

在方框506中,在接收到同步通信资源的请求之后,根复合体104的带宽管理器分析EGIO体系结构的至少一个适当子集的可用通信资源,以在方框508中确定同步通信资源的请求是否合适。 At block 506, after receiving the request for isochronous communication resources, the bandwidth of root complex 104 analyzes the available communication resources manager of at least one suitable sub-set of the EGIO architecture to determine synchronous communication resources in block 508 the request is appropriate. 根据一个实施例,根复合体104的带宽管理器分析包括了请求器和完成器之间的通信路径的与端口106、(多个)交换器108、(多条)链路112等相关联的信息,来确定是否可以满足合同步通信请求的带宽和服务延迟需求。 According to one embodiment, root complex 104 includes a bandwidth manager analyzes the request and the completion of a communication path between the port 106, (s) switches 108, (s) 112 and other associated links information, to determine whether to meet the bandwidth and service contract request further communication latency requirements. 在另一个实施例中,请求器/完成器对只是以逐个链路为基础在它们自身和任何介入元件之间建立同步协定(或关于操作参数的协商协约)如果在方框508中根复合体104的带宽管理器确定请求的通信资源不可用,则根复合体丢弃同步信道的请求,并且在方框510中可以提供所请求的资源不可用的指示。 In another embodiment, the requester / finisher for only by-link basis between themselves and any intervening elements to establish synchronization protocol (or negotiated agreement on operating parameters) in block 508. If the root complex 104 Bandwidth Manager determines that the request of communication resources are not available, the root complex drop request synchronization channel and at block 510 may provide the requested resource is unavailable instructions. 根据某些实施例,可用资源的指示会提供给请求器/完成器对,随后请求器/完成器对还是根据所指示的可用资源,可以决定重新发布同步通信资源的请求。 According to some embodiments, an indication of the available resources will be provided to the requester / complete pair, followed by a requester / complete pair or indicated in accordance with available resources, may decide to re-release synchronous communication resource requests. 在另一个实施例中,带宽管理器将通知请求了资源的实体分配了某个带宽(其可能小于所请求的)。 Example, the bandwidth manager will notify the requesting entity of resources assigned to a certain bandwidth (which may be less than the requested) in another embodiment. 在这种情况下,请求实体不需要重新发布请求。 In this case, the requesting entity is not required to re-release request.

根据一个示例性实施例,在确定是否能满足对同步通信资源的请求时,并且在方框512中建立同步协定时,根复合体104的带宽管理器如下计算请求器/完成器对的带宽需求:BW=(N*Y)/T[1]公式将分配带宽(BW)定义为在特定时间段(T)内具有特定有效载荷大小(Y)的事务的特定数目(N)的函数。 According to an exemplary embodiment, in determining whether to meet the request for isochronous communication resource, and establish synchronization protocol in block 512, the root complex 104 as bandwidth requirements Bandwidth Manager calculate requester / complete pair of : BW = specific number (N * Y) / T [1] formula allocates bandwidth (BW) is defined as having a specific payload size (Y) in a specific time period (T) within a transaction (N) function.

同步协定中的另一个重要参数是延迟。 Synchronization agreements Another important parameter is the delay. 基于协定,同步事务可以在特定的延迟(L)内完成。 Based on the agreement, the transaction can be completed in a specific synchronization delay (L) inside. 一旦带宽管理器允许请求器/完成器对进行同步通信,在常规操作条件下,完成器和介入的EGIO体系结构元件(例如,交换器、(多条)链路、根复合体等等)向请求器保证带宽和延迟。 Once Bandwidth Manager allow requester / finisher for synchronous communication, under normal operating conditions, the completion EGIO architecture elements and intervention (for example, switches, (s) links, root complex, etc.) to requester guaranteed bandwidth and latency.

因此,在方框512中产生的同步协定规定了由(多个)EGIO接口106实现的特定服务纪律,该接口106参与了EGIO体系结构中的同步通信。 Therefore, the synchronization protocol generated in block 512 are specified by a particular service discipline (s) EGIO interface 106 implemented, the EGIO interface 106 architecture involved in the synchronous communication. 以下述方式将服务纪律作用于EGIO交换器108和完成器(例如,端点110、根复合体104等等),即注入请求的服务受特定服务时间间隔(t)支配。 Service discipline in the following manner acting EGIO switches 108 and completed (e.g., endpoints 110, root complex 104, etc.), i.e., by injection of a specific service request service interval (t) dominate. 该机制用于提供当请求器发出的同步分组被处理时的控制方法。 This mechanism is used to provide a control method for synchronizing a packet request is issued when being processed.

因此,在方框514中以下述方式管理同步流量,即只有遵照协商的同步协定而被注入到EGIO体系结构的分组才允许立即前进,并且开始由EGIO体系结构元件处理。 Thus, in block 514 in the following manner synchronized traffic management, that is, only in accordance with the negotiated agreement is injected into the synchronous packet EGIO architecture are permitted to go forward immediately, and start processing the EGIO architecture elements. 通过流控制机制,阻止了试图注入比按照协商协议允许的更多的同步流量的不兼容请求器进行这样的操作,这将在下文详细描述(例如见数据链路层特征集)。 Through the flow control mechanism, preventing attempts to inject than in accordance with the negotiated agreement is not compatible with the request to allow more simultaneous traffic is carried out such an operation, which will be described in detail below (see for example the data link layer feature set).

根据一个示例性实现,同步时间段(T)被均匀的划分为多个虚拟时隙(t)的单元。 According to an exemplary implementation, the synchronization period (T) is evenly divided into a plurality of virtual timeslots (t) of the unit. 在一个虚拟时隙中最多允许一个同步请求。 In a virtual slot allows up to a synchronous request. 根据一个实施例,作为EGIO接口的数据结构中的头部信息来提供由EGIO组件支持的虚拟时隙的大小(或持续时间)。 Depending on the size (or duration) to one embodiment, a data structure of the EGIO interface header information provided by the EGIO component supports virtual slots. 在另一个实现中,在接收到初始化事件(例如,冷启动、复位等等)时,通过来自EGIO组件的广播消息来报告虚拟时隙的大小。 In another implementation, upon receipt of the initialization event (for example, cold start, reset, etc.), by broadcasting messages from the EGIO component to report the size of the virtual slot. 在另一个实现中,在接收到专用请求消息时,通过来自EGIO组件的专用信息消息来报告虚拟时隙的大小。 In another implementation, a dedicated request message is received through a dedicated information message from the EGIO component to report the size of the virtual slot. 在另一个实现中,虚拟时隙的大小可以是固定的,并且同步带宽管理器软件可以下述方式交错嵌入有效(active)和无效(inactive)时隙(在带宽分配期间),所述方式有效地创建“较宽”的时隙。 In another implementation, the size of the virtual timeslot can be fixed, and the synchronous bandwidth manager software can interleave embedded in such a manner effective (active) and inactive (inactive) time slots (during bandwidth allocation), the mode effective to create "wider" time slot.

根据一个实施例,虚拟时隙(t)的持续时间是100ns。 According to one embodiment, the virtual timeslot (t) is the duration of 100ns. 同步时间段(T)的持续时间取决于所支持的基于时间仲裁方案(例如,基于时间加权轮询(weighted round-robin,WRR)(或加权顺序))的阶段(phase)数目。 Synchronization period (T) of the duration depends on the support of time-based arbitration scheme (for example, time-based WRR (weighted round-robin, WRR) (or weighted sequence)) of the phase (phase) number. 根据一个实施例,阶段数目由同步虚拟时隙的数目规定,并且由每个元件中保持的端口仲裁表中的条目数目指示。 According to one embodiment, the number of stages defined by the number of simultaneous virtual slots and held by each element in the port arbitration table indicates the number of entries. 当端口仲裁表大小等于128时,在同步时间段中有128个虚拟时隙(t),即,T=12.8μs。 When the port arbitration table size equals 128, there are 128 virtual timeslots (t) in the synchronization period, that is, T = 12.8μs.

根据一个示例性实施例,在EGIO配置期间建立同步事务的最大有效载荷大小(Y)。 According to an exemplary embodiment, establishing synchronous transactions during EGIO configuration maximum payload size (Y). 在配置之后,在给定EGIO层次域最大有效载荷大小是固定的。 After you configure a given EGIO hierarchy domain maximum payload size is fixed. 固定最大有效载荷大小的值被用于同步带宽预算,而不考虑与请求器/完成器之间的同步事务相关联的数据有效载荷的实际大小。 Fixed maximum payload size of the bandwidth is used to synchronize the budget without considering the actual size of the data requester / complete synchronization between transactions associated payload.

在讨论了同步时间段(T)、虚拟时隙(t)和最大有效载荷(Y)的条件下,时间段中的虚拟时隙的最大数目是:Nmax=T/t[2]并且,最大可指定同步带宽是:BWmax=Y/t[3]从而,同步带宽可以分配的粒度(granularity)定义如下:BW粒度=Y/T[4]将同步带宽BW链路分配给通信链路112与按照每个同步时间段(T)分配N链路虚拟时隙相类似,其中N链路由下式给出:N链路=BW链路/BW粒度[5]为了保持对链路的受调节的访问,用作同步流量的出口(egressport)的交换器端口建立具有多达Nmax个条目的数据结构,其中Nmax是在给定链路带宽、粒度和延迟需求的条件下容许的同步会话的最大数目。 Under conditions discussed synchronization period (T), the virtual time slot (t) and the maximum payload (Y), the maximum number of virtual time slots is: Nmax = T / t [2] and the maximum You can specify synchronous bandwidth: BWmax = Y / t [3] Thus, the synchronous bandwidth allocation granularity (granularity) is defined as follows: BW size = Y / T [4] The synchronous link bandwidth BW assigned to the communication link 112 N time slots allocated for each virtual link synchronization period (T) are similar, where N link is given by: N = BW link Link / BW size [5] In order to maintain the link by adjusting Access, used to synchronize the flow of exports (egressport) of switch ports to establish a data structure entries with up to Nmax, Nmax is the largest under the conditions given link bandwidth, granularity and latency requirements of acceptable sync session number. 表中的一个条目代表同步时间段(T)中的一个虚拟时隙。 Entry represents the table synchronization period (T) of a virtual slot. 当表条目被给定端口号码(PN)的值时,意味着该时隙被分配给由端口号码指定的入口(ingress port)。 When the table entry is given port number (PN) value means that the time slot is assigned to the port number specified by the entrance (ingress port). 因此,当端口仲裁表中的N链路条目被给定了PN的值时,N链路虚拟时隙被分配给入口。 Therefore, when the port arbitration table N link entries are given the value of PN, N link virtual slots are allocated to the entrance. 只有当由出口的同步时间计数器(其每隔t时间增加1,并且当到达T时重新开始计数)访问的表条目被设定为PN时,出口才会容许来自入口的对其它服务的一个同步请求事务。 Only when the export synchronization time counter (which increased by one every t time, and when reaching T to start counting again) table entry access is set to PN, which will permit the export of other services from the inlet of a synchronous request transaction. 即使在入口中准备好了待处理的同步请求,直到下一轮仲裁(例如,基于时间、加权轮询(WRR)仲裁)才会处理它。 Even a good preparation in the inlet synchronization request pending until the next round of arbitration (for example, time-based, weighted round-robin (WRR) arbitration) will handle it. 以此方式,基于时间的端口仲裁数据结构用作同步带宽分配和流量调节。 In this way, a time-based port arbitration data structure is used as synchronous bandwidth allocation and flow regulation.

如这里所使用的,上面讨论的事务延迟由通过EGIO组织结构的延迟和完成器产生的延迟两者组成。 As used herein, the matters discussed above, both delayed by the delay generated by the delay EGIO organizational structure and complete composition. 为每个事务定义同步事务延迟,并且以虚拟时隙t为单位测量同步事务延迟。 For each transaction definition synchronous transaction latency, and virtual slot t measured in units of synchronous transaction latency.

对于端点到根复合体通信模型中的请求器,读取延迟定义为往返程延迟,即,从设备向它的事务层递交存储器读取请求分组(在发送方)时到对应的读取完成到达设备的事务层(接收方)时的延时。 For end-to-root complex communication model requestor, read latency is defined as the round-trip delay, that is, from device to its submission memory read request transaction layer packet (the sender) to the corresponding read completion time arrival Delay Transaction Layer (receiver) devices when. 对于任一个通信模型中的请求器,写入延迟定义为从请求器发送存储器写入请求到其事务层的发送端时到数据写入变得在完成器的存储器子系统中全局可见时的延时。 Data is written to the completion of the extension to become globally visible memory subsystem when a communication model for any of the requester, write latency is defined as the sending memory write request from the requestor to the sender its transaction layer time. 当访问存储器地址的所有代理获得更新数据时,对存储器的写入达到全局可见的情况。 When accessing the memory address of all agents obtain updated data is written to the memory of reach globally visible situation.

作为同步协定的一部分,提供了同步事务延迟的上边界和下边界。 As part of the synchronization agreement, it provided on the boundary and the lower boundary synchronization transaction delays. 请求器中的同步数据缓冲器大小可以使用最小和最大同步事务延迟来确定。 Requestor synchronous data buffer size can be used to synchronize the minimum and maximum transaction delay to determine. 如下文所详细介绍的,最小同步事务延迟比最大同步事务延迟小得多。 As will be described in detail, the minimum synchronous transaction latency is much smaller than the maximum synchronous transaction latency.

对于请求器,可以根据下面的等式(6)来计算最大同步(读取或写入)事务延迟(L),L=L组织结构+L完成器[6]其中L组织结构是EGIO组织结构的最大延迟,而L完成器是完成器的最大延迟。 For requests that can be calculated according to the following equation (6) Maximum synchronization (read or write) transaction latency (L), L = L + L complete organizational structure [6] where L is EGIO organizational structure organizational structure The maximum delay, and L is the completion of the maximum delay in completion.

EGIO链路112或EGIO组织结构的事务延迟定义为从事务在发送端公布时到它在接收端可用时的延时。 EGIO EGIO link 112 or transaction delays define the organizational structure from the transaction announced at the sending end to it for the delay in the receiving end is available. 这适用于读取和写入事务两者。 This applies to both read and write transactions. 在这方面,L组织结构取决于拓扑结构、由每条链路112引起的延迟以及从请求器到完成器的路径中的仲裁点。 In this regard, L organizational structure depends on the topology, the delay caused by the each link 112 and a path from the requestor to complete the arbitration point.

继续参考图5,过程前进到方框516,其中带宽管理器确定同步通信信道的使用是否完成。 With continuing reference to FIG. 5, the process proceeds to block 516, bandwidth manager determines which communication channel to use synchronization is complete. 即,带宽管理器确定同步通信对话是否已经结束,并且因而确定为支持同步信道而分配的虚拟信道资源是否可被释放而由EGIO组织结构使用。 That is, the bandwidth manager determines whether the synchronous communication session has ended, and thereby determining whether to support a synchronization channel allocated virtual channel resources can be freed and used by EGIO structure. 根据一个实施例,带宽管理器从一个或多个请求器/完成器对接收指示,即不再需要同步资源的指示。 According to one embodiment, bandwidth manager from one or more of the requester / completed implementation of the device receiving an indication that no longer needs to be instructed to synchronize resources. 在另一个实施例中,在某个无效时间段之后带宽管理器推断出同步通信已经结束。 In another embodiment, the period of time after an invalid bandwidth manager infer synchronous communication has ended.

如果在方框516中带宽管理器确定同步通信没有结束,则过程回到方框514。 If in block 516 bandwidth manager determines that synchronous communication is not over, the process returns to block 514.

或者,过程前进到方框518,其中带宽管理器取消同步协定,从而释放该带宽以支持余下的虚拟信道。 Alternatively, the process proceeds to block 518 where the bandwidth manager to cancel the synchronization agreements, freeing the bandwidth to support the rest of the virtual channel. 根据一个实施例,带宽管理器通知EGIO体系结构的一个或多个其他元件,同步协议不再有效。 According to one embodiment, bandwidth manager notify one or more other elements, the synchronization protocol EGIO architecture is no longer valid.

事务排序尽管使所有响应依次序被处理可能更简单,但是事务层202试图通过准许事务的重新排序来提高性能。 Transaction ordering Despite all responses are processed in order, it may be easier, but the transaction layer 202 attempts to permit the transaction reordering to improve performance. 为了便于这样的重新排序,事务层202“标记”事务。 To facilitate such re-ordering, transaction layer 202 "tags" transactions. 即根据一个实施例,事务层202添加事务描述符到每个分组,使得它的传输时间可以由EGIO体系结构中的元件来优化(例如,通过重新排序),且不会丢失分组最初被处理的相对顺序。 That is, according to one embodiment, transaction layer 202 adds the transaction descriptor to each packet such that its transmit time may be made EGIO architecture elements to optimize (e.g., by re-ordering), and without losing the packet was originally processed The relative order. 这样的事务描述符被用于帮助请求和完成分组通过EGIO接口层次而进行路由。 Such a transaction descriptor is used to help requests and completed by EGIO interface hierarchy and packet routing.

因而,EGIO互连体系结构和通信协议的创新方面之一是它提供了不依顺序通信,从而通过减少空闲或等待状态来提高数据吞吐量。 Thus, one of the innovative EGIO interconnection architecture and aspects of the communication protocol is that it provides a failing communication sequence, so that by reducing the idle or wait states to increase data throughput. 在这方面,事务层202使用了一组规则来定义EGIO事务的排序需求。 In this regard, the transaction layer 202 uses a set of rules to define the sequencing requirement EGIO transactions. 定义了事务排序需求来确保软件的正确操作,所述软件被设计成支持生产者一消费者排序模型,同时允许基于不同排序模型(例如,图形附着应用的松散排序)的应用的改进的事务操作灵活性。 Defines the transaction ordering needs to ensure proper operation of the software, the software is designed to support a consumer ordering model producer, while allowing to improve the application of different sort of model (for example, graphics applications, loosely attached order) based on transactional operations flexibility. 下文描述了两种不同类型的排序需求:单个排序平面模型和多个排序平面模型。 The following describes the two different types of sequencing requirements: a single sort plane models and multiple ordering plane model.

·基本事务排序一单个“排序平面”模型假定以下两个组件通过与图1相似的EGIO体系结构连接起来:存储器控制集线器,提供到主处理器和存储器子系统的接口;以及IO控制集线器,提供到IO子系统的接口。 · Basic transaction ordering a single "ordering plane" model assumes that the following two components together with a similar diagram by EGIO architecture: the memory controller hub, providing an interface to the host processor and the memory subsystem; and IO controller hub, providing interface to IO subsystem. 两个集线器都含有用于操作输入和输出流量的内部队列,并且在这个简单模型中所有IO流量都被映射到单个“排序平面”。 Two hubs contain internal queues are used to operate inbound and outbound traffic, and in this simple model all IO traffic is mapped to a single "ordering plane." (注意,事务描述符源ID信息为EGIO层次中的每个代理都提供了唯一的标识符,还要注意,映射到源ID的IO流量可以携带不同事务排序属性)。 (Note that the transaction descriptor source ID information EGIO hierarchy Each agent provides a unique identifier, note that mapped to the IO traffic source ID can carry different transaction ordering attributes). 在IO发起(IO-initiated)的流量和主发起(host-initiated)的流量之间规定了本系统配置的排序规则。 The system configuration provides collation between the initiator (IO-initiated) at IO traffic and the main launch (host-initiated) traffic. 根据上述说法,映射到源ID的IO流量和主处理器发起的流量代表在单个“排序平面”中传递的流量。 According to the statement, is mapped to the source ID of IO traffic flow and traffic initiated on behalf of the main processor in a single pass "Sort flat" in.

参考表II,下面提供了该事务排序规则的示例。 Referring to Table II, below provides an example of the transaction ordering rules. 该表中定义的规则普遍适用于包括存储器、IO配置和消息的EGIO系统中的所有类型的事务。 The rules defined in the table apply generally to include memory, IO configuration and message EGIO system for all types of transactions. 在下面的表II中,列代表两个事务的第一个,而行代表第二个。 In the following Table II, column represents the first two transactions, the line for the second. 表条目指明了两个事务之间的排序关系。 Table entry indicates the sort of relationship between the two transactions. 表条目定义如下:是—一般会允许第二个事务超过第一个事务以避免死锁。 Table entries are defined as follows: Yes - generally allow a second transaction exceeds a transaction to avoid deadlocks. (当发生阻塞时,需要第二个事务超过第一个事务。一般应当考虑公平以防止饥饿(starvation))。 (When blocking, we need a second transaction exceeds a transaction generally should be considered fair to prevent starvation (starvation)).

Y/N—没有需求。 Y / N- no demand. 第一个事务可选地超过第二个事务或者被其阻塞。 Alternatively, the first transaction of more than a second transaction on or be blocked.

否—一般不会允许第二个事务超过第一个事务。 No - generally does not allow a second transaction exceeds a transaction. 这需要保持严格的排序。 This need to maintain strict order.

表II:单个排序平面的事务排序和死锁避免 Table II: transaction ordering a single sort plane and deadlock avoidance

表III:事务排序解释·高级事务排序—“多个平面”事务排序模型前述部分定义了单个“排序平面”内的排序规则。 Table III: transaction Explanation Sort advanced transaction ordering - "multiple planes" transaction ordering model of the preceding section defines the collation single "ordering plane" inside. 如上所述,EGIO互连体系结构和通信协议使用唯一的事务描述符机制来关联事务和额外的信息,以支持更复杂的排序关系。 As described above, EGIO interconnection architecture and communication protocol uses a unique transaction descriptor mechanism associated with the transaction and additional information to support more sophisticated ordering relationships. 事务描述符中的字段允许创建多个“排序平面”,从IO流量排序来看这些排序平面是互相独立的。 Transaction descriptor field allows you to create multiple "ordering plane" from the IO traffic ordering look at these sort of planes are independent of each other.

每个“排序平面”都包括对应于具体IO设备(由唯一的源ID指定)的排队/缓冲逻辑以及传输主处理器发起的流量的排队/缓冲逻辑。 Each queue "Sort flat" includes queue corresponding to specific IO device (designated by a unique source ID) of / buffer logic and transmitting traffic initiated by the host processor / buffer logic. “平面”内的排序一般只在这两者之间定义。 Sort "flat" within the generally defined between the two. 对独立于其它“排序平面”的每个“排序平面”都实施了在前述部分规定的用来支持生产者/消费者用途模型并且防止死锁的规则。 Independent of other "ordering plane" each "ordering plane" have implemented rules deadlock to support producer / consumer model and to prevent the use specified in the preceding section. 例如,由“平面”N发起的请求的读取完成可以绕过由“平面”M发起的请求的读取完成。 For example, reading from the "flat" N-initiated request of finished reading can bypass the "flat" M-initiated request is completed. 然而,平面N的读取完成和平面M的读取完成都不能绕过由主机发起的公布存储器写入。 However, the reading is completed and the plane M N finished reading plane can not be bypassed by the host-initiated release memory write.

尽管平面映射机制的使用允许存在多个排序平面,但是排序平面中的一些或全部可以“折叠”到一起以简化实现(即,将多个单独控制的缓冲器/FIFO结合成单个)。 Although the use of the plane mapping mechanism permits the existence of multiple ordering plane, but sort of flat, some or all of which may "fold" together to simplify the implementation (ie combining multiple separately controlled buffer / FIFO as a single). 当所有平面折叠在一起时,仅使用事务描述符源ID机制来帮助事务的路由,并且它不用于在IO流量的独立流之间松散排序。 When all the plane folded together using only the transaction ID descriptor source routing mechanism to help matters, and it is not used between the individual flow loose sort IO traffic.

除了上述的内容,事务描述符机制规定了使用排序属性在单个排序平面内修改缺省排序。 In addition to the content, transaction descriptor mechanism provides for using a sort attribute to modify the default ordering within a single ordering plane. 从而可以以每个事务为基础而控制排序的修改。 Thereby per transaction basis and control modifications ordered.

事务层协议分组格式如上所述,创新EGIO体系结构使用基于分组的协议以在相互通信的两个设备的事务层之间交换信息。 Transaction Layer Protocol Packet Format As described above, innovative EGIO architecture uses a packet-based transaction layer protocol between the two devices communicate with each other to exchange information. EGIO体系结构通常支持存储器、IO、配置和消息事务类型。 EGIO architecture generally supports the Memory, IO, Configuration and Messages transaction types. 一般使用要求或完成分组运送这些事务,其中只有当要求时,即要求返回数据或请求事务的确认接收时,才使用完成分组。 When general packet transport requirements or to complete these transactions, only when the requirement that return data or requests confirmation transaction received only used to complete the grouping.

参考图9,根据本发明的教导示出了示例性事务层协议的示图。 9, according to the teachings of the present invention shows a diagram of an exemplary transaction layer protocol. 根据图9所图示的示例性实现,图示的TLP头部900包括格式字段、类型字段、扩展类型/扩展长度(ET/EL)字段和长度字段。 According to the illustrated exemplary implementation of FIG. 9, illustrated TLP head 900 includes a format field, type field, the extended type / extended length (ET / EL) field and the length field. 应当知道,某些TLP在头部之后包括如头部中列出的格式字段确定的数据。 It should be known that certain TLP format field after head comprises listed as the head of the data determined. 没有TLP可以含有多于MAX_PAYLOAD_SIZE设定的极限的数据。 TLP can contain no more than the limit set MAX_PAYLOAD_SIZE data. 根据一个示例性实现,TLP数据是4字节自然对齐的,并且以4字节双字(DW)增加。 According to one example implementation, TLP data is four-byte naturally aligned and in 4-byte double word (DW) is increased.

如这里所使用的,根据下面的定义格式(FMT)字段规定了TLP的格式: As used herein, the following definitions according to the format (FMT) field specifies the format of the TLP:

·000-2DW头部,无数据·001-3DW头部,无数据·010-4DW头部,无数据·101-3DW头部,有数据·110-4DW头部,有数据·预留所有其它的编码类型字段用于指示TLP中使用的类型编码。 · 000-2DW head, no data · 001-3DW head, no data · 010-4DW head, no data · 101-3DW head, the data · 110-4DW head aside all other data * encoding type field indicates the type of coding used TLP. 根据一个实现,一般应该解码格式[2:0]和类型[3:0]两者来确定TLP格式。 According to one implementation, the general should decoding format [2: 0] and type [3: 0] to determine both the TLP format. 根据一个实现,类型[3:0]字段中的值用于确定扩展类型/扩展长度字段是否被用于扩展类型字段或长度字段。 According to one implementation, type [3: 0] field is used to determine the type of expansion / extension is used to extend the length of the field is a type field or length field. ET/EL字段一般只用于扩展存储器类型读取请求的长度字段。 ET / EL field is generally used only for the length of the field type of extended memory read request.

长度字段提供了有效载荷长度的指示,还是以DW增加,如下所示::0000 0000=1DW:0000 0001=2DW:....... Length field provides an indication of the length of the payload, or to DW increase as follows :: 0000 0000 = 1DW: 0000 0001 = 2DW: .......

:1111 1111=256DW下面提供了示例性TLP事务类型的至少一个子集、它们对应的头部格式以及描述的总结,表IV中: : 1111 1111 = 256DW below provides at least a subset of example TLP transaction types and their corresponding header format and a summary description of Table IV:

表IV:TLP类型总结附录A中提供了有关请求和完成的其它细节,其中的说明在这里作为参考而被明确引入。 Table IV: TLP type A summary is provided in the request and other details complete the appendix, which is described herein are expressly incorporated herein by reference.

流控制与传统流控制方案普遍关联的限制之一是它们对可能发生的问题有反应(reactive),而不是在预先(proactively)降低发生这些问题首先发生的机会。 One of the limitations of traditional flow control and flow control scheme is generally associated with their problem may occur responsive (reactive), rather than the opportunity to advance (proactively) to reduce the occurrence of these problems occurring in the first. 例如在传统的PCI系统中,发送者将向接收者发送信息直到它接收到停止/中止发送的消息。 For example, in a conventional PCI system, the sender will send a message receiver until it receives a Stop / abort message sent. 其中停止/中止发送直到下一个通知。 Wherein the stop / suspend transmission until a next notification. 这些请求随后可以跟随有重新发送起始于发送的给定点处的分组的请求。 These requests can then be followed by a request to resend the packet at the starting point to be sent. 而且,目前这样的流控制机制是基于硬件的,它们不适合上述动态建立、独立管理的虚拟信道应用。 Moreover, the current flow control mechanism such hardware-based, they are not suitable for the above dynamic is established, independent management of virtual channel applications. 本领域技术人员将理解,这一反应(reactive)方法导致周期浪费,并且在这方面可能效率较低。 Those skilled in the art will appreciate that this reaction (reactive) method results in wasted cycles and may be less efficient in this respect.

为了解决这个限制,EGIO接口106的事务层202包括流控制机制,其预先降低发生溢出情况的机会,同时还规定以发起者和(多个)完成者之间建立的虚拟信道的每个链路为基础来遵守排序规则。 To address this limitation, the flow control mechanism 202 includes a transaction layer EGIO interface 106, which reduces the chance of overflow conditions in advance, and also requires that each link in between the initiator and (s) completed by the establishment of virtual channels as a basis for compliance with the collation.

根据本发明的一个方面,引入了流控制“信用”的概念,其中接收者共享下列信息:(a)缓冲器(信用)大小,和(b)对于发送者和接收者之间建立的每条虚拟信道(即以每条虚拟信道为基础)的发送者当前可用缓冲器空间。 According to one aspect of the present invention, the introduction of flow control "credit" concept, in which the receiver share the following information: (a) buffer (credit) size, and (b) between the sender and receiver for the establishment of each virtual channel (ie for each virtual channel basis) sender buffer space currently available. 这使得发送者的事务层202能够保持可用缓冲器空间的估值(例如,可用信用的计数),并且如果确定发送将在接收缓冲器内产生溢出情况则能够预先节流通过任何虚拟信道进行的发送,其中所述可用缓冲器空间分配给通过被识别的虚拟信道进行的发送。 This allows the sender of the transaction layer 202 to maintain the available buffer space valuation (e.g., a count of available credits), and transmits the generated if it is determined in the reception buffer overflow condition it is possible to advance the throttle by any of the virtual channel Send wherein the transmission buffer space is allocated to be identified by a virtual channel is available.

根据本发明的一个方面,如上所述,事务层202有选择地调用流控制来防止与虚拟信道相关联的接收缓冲器的溢出并且能够遵循排序规则。 According to one aspect of the present invention, as described above, the transaction layer 202 is selectively controlled to prevent the overflow call flow associated with the virtual channel associated with the receive buffer and to follow collation. 根据一个实现,由发送者使用处理层202的流控制机制以通过EGIO链路112来跟踪代理(接收者)中的可用队列/缓冲器空间。 According to one implementation, the sender uses flow control mechanisms to deal with layer 202 by EGIO link 112 to track agent (receiver) available in the queue / buffer space. 在这方面,与传统的流控制机制不同,发送者而非接收者负责确定何时接收者暂时不能通过虚拟信道接收更多内容。 In this regard, the traditional flow control mechanisms, the sender is responsible for determining when the recipient rather than the recipient through a virtual channel is temporarily unable to receive more. 如这里所使用的,流控制没有暗示请求已经到达它的最终完成器。 As used herein, flow control does not imply a request has reached its final finisher.

在EGIO体系结构中,流控制与数据完整性机制相互独立,其中所述数据完整性机制用于实现发送者和接收者之间的可靠信息交换。 In the EGIO architecture, flow control and data integrity mechanisms independent of each other, wherein the data integrity mechanisms used to implement reliable information exchange between sender and receiver. 即,流控制能够保证从发送者到接收者的事务层分组(TLP)信息流完好,这是由于数据完整性机制(下文讨论)保证通过重新传输改正错误的和丢失的TLP。 That is, the flow control to ensure that from the sender to the recipient of the transaction layer packet (TLP) information flow intact, this is because the data integrity mechanisms (discussed below) to ensure that retransmission by correcting errors and loss of TLP. 如这里所使用的,事务层的流控制机制包括EGIO链路112的虚拟信道。 As used herein, the flow control mechanism of the transaction layer comprises EGIO link 112 virtual channels. 在这方面,将在由接收者通告的流控制信用(FCC)中反映由接收者支持的每个虚拟信道。 In this regard, the announcement by the recipient of flow control credits (FCC) reflected by the receiver supports each virtual channel.

根据一个示例性实现,由事务层202和数据链路层204合作来执行流控制。 According to an exemplary implementation, the transaction layer 202 and the data link layer 204 cooperate to perform flow control. 即,使用数据链路层分组(DLLP)在EGIO链路112的两端之间(例如,以每个VC为基础)传输流控制信息,以由事务层202的流控制机制使用。 That is, the data link layer packet (DLLP) between the ends of the EGIO link 112 (e.g., on a per-VC basis) transmitting flow control information to be used by the flow control mechanism of the transaction layer 202. 为了方便描述流控制机制,区分出下列分组信息类型或流控制信用类型:(a)公布请求头部(PH)(b)公布请求数据(PD)(c)非公布请求头部(NPH)(d)非公布请求数据(NPD)(e)读取、写入和消息完成头部(CPLH)(f)读取和消息完成数据(CPLD) To facilitate the flow control mechanism is described, and distinguish a flow control packet information type or types of credit: (a) announce the request header (PH) (b) publish the requested data (PD) (c) non-publication request header (NPH) ( d) non-publication request data (NPD) (e) to read, write, and completion of the message header (CPLH) (f) to read and complete data message (CPLD)

如上所述,预先流控制的EGIO实现中的测量单元是流控制信用(FCC)。 As described above, in advance for control of EGIO flow measurement unit is a flow control credits (FCC). 根据仅仅一个实现,对于数据,流控制信用是十六(16)字节。 According to just one implementation, the data flow control credit is sixteen (16) bytes. 对于头部,流控制信用的单元是一个头部。 For the head, flow control credit is a head unit. 如上所述,每个虚拟信道都保持了独立流控制。 As described above, each virtual channel has maintained a separate flow control. 因此,事务层202中的流控制机制为分组信息的每个前述类型(如上所述的(a)-(f))以每个VC为基础来维持并跟踪信用的单独的指示符。 Therefore, the transaction layer 202 flow control mechanism for each of the aforementioned type packet of information (as described above (a) - (f)) to each VC basis to maintain and track the credit of individual indicator. 根据所图示的示例性实现,分组的发送根据下述内容来消耗流控制信用:-存储器/IO/配置读取请求:1NPH单元-存储器写入请求:1PH+nPD单元(其中n与数据有效载荷的大小相关联,例如由流控制单元大小(例如,16字节)划分的数据的长度)-IO/配置写入请求:1NPH+1NPD-消息请求:取决于消息,至少1PH和/或1NPH单元-带有数据的完成:1CPLH+nCPLD单元(其中n与由诸如16字节的流控制数据单元大小划分的数据大小有关)-没有数据的完成:1CPLH对于所跟踪的每种类型的信息,有三个概念寄存器来监测消耗的信用(发送者内)、信用极限(发送者内)和分配的信用(接收者内),每个概念寄存器有八(8)比特宽。 According to the illustrated exemplary implementation, transmission packet according to the following content to consume flow control credits: - memory / IO / Configuration read requests: 1NPH unit - a memory write request: 1PH + nPD units (wherein n and the data is valid size of the load associated with, such as the length of the flow control unit size (for example, 16 bytes) of data partition) -IO / configuration write request: 1NPH + 1NPD- message request: depends on the message, at least 1PH and / or 1NPH unit - completed with data: 1CPLH + nCPLD units (wherein n and by the flow control data unit size of 16 bytes is divided as the size of the data) - No data is completed: 1CPLH tracked for each type of information, There are three concepts registers to monitor the consumption of credit (within the sender), credit limit (within the sender) and the distribution of credit (within the receiver), each concept register has eight (8) bits wide. 信用消耗寄存器含有自从初始化以来所消耗的流控制单元的例如模256的总量的计数。 Credit consumption register contains the flow control unit consumed since initialization count mode, for example, 256 of the total. 已经引入了流控制机制的体系元件,参考图6,示出了初始化和操作的示例性方法。 Has introduced a system component flow control mechanism, with reference to Figure 6, there is shown an exemplary method of initialization and operation.

图6是根据本发明的仅仅一个示例性实施例的EGIO体系结构的流控制机制的示例性操作方法的流程图。 Figure 6 is a flowchart of an exemplary method of operation of the flow control mechanism EGIO architecture of an exemplary embodiment of the present invention only. 根据图6所图示的示例性实现,方法从方框602开始,其中当硬件初始化或复位时,初始化这里所描述的与至少一个初始虚拟信道相关联的流控制机制。 According to the illustrated exemplary implementation of FIG. 6, the method starting from block 602, wherein when the hardware initialization or reset, initialization and at least one initial virtual channel flow control mechanism associated described herein. 根据一个示例性实现,当初始化EGIO元件的EGIO接口106的数据链路层204时,初始化与VC0(例如,用于大量(bulk)通信的缺省虚拟信道)相关联的流控制机制。 According to an exemplary implementation, when the data link layer device initialization EGIO EGIO interface 106 of 204, initialization and VC0 (for example, the default for bulk (bulk) of virtual communication channel) flow control mechanism associated with it.

在方框604中,事务层202的流控制机制更新一个或多个流控制寄存器的参数。 In block 604, the flow control mechanism of the transaction layer 202 of updating one or more flow control parameter register. 即,在初始化时信用消耗寄存器被设定为全零(0),并且当事务层承诺发送信息到数据链路层时增加。 That is, when initialization credit consumed register is set to all zeros (0), and increases when the transaction layer promised to send information to the data link layer. 增加的大小与承诺发送的信息消耗的信用数量有关。 Increased size and number of credits commitment to send information about consumption. 根据一个实现,当达到或超过最大计数(例如,全1)时,计数器翻转为零。 According to a realization, when it reaches or exceeds the maximum count (for example, a full 1), the counter rolls over to zero. 根据一个实现,使用无符号8比特模算术来维持计数器。 According to one implementation, unsigned 8-bit modular arithmetic to maintain the counter.

在发送者中保持的信用极限寄存器含有可能消耗的流控制单元的最大数值的极限。 Limit the sender to maintain the credit limit register contains the flow control unit may consume maximum value. 在接口初始化(例如,启动、复位等)后,信用极限寄存器设定为全零,并且随后在接收消息后被更新以反映在流控制更新消息(上文进行了描述)中指示的值。 In the interface initialization (for example, start, reset, etc.), the credit limit register is set to all zeros, and then update the value to reflect the flow control update message (has been described above) indicated in after receiving a message.

在接收者中保持的信用分配寄存器保持了自从初始化以来授与发送者的信用总数的计数。 The recipient to maintain credit allocation register maintained since the initialization of the credit granted with the sender of the total count. 根据接收者的缓冲器大小和分配策略来初始设定该计数。 According to the receiver buffer size and allocation policies to set the initial count. 该值可以包括在流控制更新消息中。 This value may be included in flow control update message.

在方框606中,EGIO接口106确定是否需要额外的虚拟信道,即除缺省VC0之外。 In block 606, EGIO interface 106 to determine whether additional virtual channel, ie other than the default VC0. 如果是这样,随着建立这些额外VC,则在方框608中事务层初始化与这些VC相关联的流控制机制,进而更新(多个)流控制寄存器。 If so, with the establishment of the additional VC, the transaction layer in block 608 is initialized with these flow control mechanisms associated VC, and then update (s) flow control registers.

如上所述,当初始化与虚拟信道相关联的流控制机制时,值随着接收者事务层从它的接收缓冲器移除已处理的信息而增加。 As described above, when the initialization associated with the virtual channel flow control mechanism associated, the value of information as the recipient of the transaction layer receive buffer is removed from its processed increases. 增加的大小与产生可用空间的大小有关。 Increase the size of the available space and produce relevant. 根据一个实施例,接收者一般会将分配的信用最初设定为等于或大于下列值的值:-PH:1流控制单元(FCU);-PD:FCU等于设备最大有效载荷大小的极大可能设定-NPH:1FCU-NPD:FCU等于设备最大有效载荷大小的极大可能设定-交换设备-CPLH:1FCU-交换设备-CPLD:FCU等于设备最大有效载荷大小的极大可能设定和设备将产生的极大读取请求中的较小的一个。 According to one embodiment of the credit, the recipient will normally allocated initially set to be equal to or greater than the value of the following values: -PH: 1 flow control unit (FCU); - PD: FCU equal to the maximum payload size of the device most likely Setting -NPH: 1FCU-NPD: FCU equal to the maximum payload size of the device most likely set - switching equipment -CPLH: 1FCU- switching equipment -CPLD: FCU equal to the maximum payload size of the device most likely set and equipment great read request will result in a smaller one.

-根和端点设备-CPLH或CPLD:255FCU(全1),发送者认为该值无穷大,因而其从不会阻塞。 - Root and endpoint devices -CPLH or CPLD: 255FCU (all 1), the sender that the infinite value, and therefore it does not clog from. 根据这样的实现,接收者一般不会为任何消息类型而将信用分配寄存器值设定为大于127FCU。 With this realization, the recipient is generally not of any message type and the credit allocation register value is set to be larger than 127FCU.

根据另一个实现,与上述使用计数器方法保持信用分配寄存器不同,接收者(或发送者)可以基于下述等式动态计算可用的信用:C_A=(最近接收的发送的信用单元数值)+(可用的接收缓冲器空间)[7]如上所述,发送者将为发送者将使用的每个虚拟信道实现概念寄存器(消耗的信用,信用极限)。 Another achieve and maintain credit allocation register, the recipient (or sender) and said using the counter method can dynamically calculate the available credit based on the following equation based on: C_A = (credit unit value last received transmission) + (available receive buffer space) [7] As described above, each virtual channel sender will be the sender will use to achieve the concept of registers (credit consumed, credit limit). 类似地,接收者为接收者支持的每个虚拟信道实现概念寄存器。 Similarly, the recipient is the recipient of each virtual channel support to realize the concept of registers. 一旦为适合的VC建立了(多个)流控制寄存器,随着过程前进到方框610,EGIO接口106就准备好参与EGIO通信。 Once established as appropriate VC (s) flow control registers, as the process proceeds to block 610, EGIO interface 106 is ready to participate in EGIO communications.

在方框610中,发送者中的EGIO接口106接收数据报用于沿着VC发送。 In block 610, the sender of the EGIO interface 106 for receiving data packets sent along the VC. 在方框612中,在发送所接收的数据报之前,用来发送数据报通过EGIO链路的EGIO元件的事务层202中的流控制机制证实该发送不会导致接收者处的溢出情况。 In block 612, before sending the received data packets for transmitting data packets through the transaction layer 202 EGIO element EGIO link flow control mechanism confirmed the transmission does not cause an overflow condition at the receiver. 根据一个示例性实现,事务层202的流控制机制基于或至少部分基于使用可用寄存器以及发送数据报将消耗的信用数量来作出这个确认。 According to an exemplary implementation, the flow control mechanism of the transaction layer 202 or at least partially based on the number of credits based on the use of available registers and transmitting data packets will be consumed to make this confirmation.

为了预先制止如果这样做将引起接收缓冲器溢出的信息的发送,如果消耗的信用的计数加上与将要发送的数据相关的信用单元的数目,小于或等于信用单元值,则允许发送者发送一类信息,即:Cred_Req=(Cred_Consumed+<Info_cred>)mod 2[字段大小][8]其中字段大小对于PH、NPH、CLPH等于八(8),对于PD、NPD和CPLD等于十二(12)。 In order to pre-empt if doing so would cause a message receive buffer overflow, if consumed credit count plus the number of data to be transmitted associated credit unit value less than or equal to the credit unit, allows the sender to send a class information, namely: Cred_Req = (Cred_Consumed + & lt; Info_cred & gt;) mod 2 [field size] [8] where the field size for PH, NPH, CLPH equal to eight (8), the PD, NPD and CPLD equal to twelve (12 ).

当发送者接收指示非无穷信用(即,<255FCU)的完成的流控制信息时,发送者将根据可用信用来节流完成。 When the sender receives a non-infinite credit instruction (ie, <255FCU) of the completion of the flow control information, the sender will be completed according to available credit throttle. 当考虑信用使用及返回时,来自不同事务的信息不混合在一个信用中。 When considering credit use and return, information from different transactions are not mixed in a credit. 类似地,当考虑信用使用及返回时,来自一个事务的头部和数据信息也从不混合在一个使用中。 Similarly, when considering credit use and return, header and data information from a transaction never be mixed in a use. 因此,当某个分组由于缺乏流控制信用而被阻塞传输时,发送者在确定应当准许哪个类型的分组绕过“停滞”分组时将遵循排序规则(上文)。 Therefore, when a packet flow control due to lack of credit is blocked transmission, the sender should be permitted to determine which type of packet bypassed "stagnation" will follow the ordering rules (above) when the grouping.

如果在方框612中流控制机制确定接收者没有合适的缓冲器空间来接收数据报,则流控制机制暂时中止沿相关虚拟信道的发送,直到发送者的(多个)流控制寄存器进行了更新以准许该发送,如方框614所示。 If it is determined there is no suitable recipient buffer space in block 612 flow control mechanism to receive data packets, the flow control mechanism to suspend sending along the associated virtual channel until the sender (s) flow control registers are updated to permit the transmission, as shown in block 614. 根据一个示例性实施例,通过流控制更新消息来接收更新,下文将对此进行详细描述。 According to an exemplary embodiment, update messages to receive updates through the flow control, as will be described in detail.

如果在方框612中,流控制机制推断出数据报的发送不会导致接收者处的溢出情况,则EGIO接口106开始发送数据报,如方框616所示。 If at block 612, the flow control mechanism to send data packets to infer does not result in an overflow condition at the receiver, the EGIO interface 106 starts sending data packets, as shown in block 616. 如上所述,数据报的发送涉及事务层202、数据链路层204和/或物理层206处的处理步骤(例如,添加头部、数据完整性信息等等)。 Send described above, involving a transaction layer packet 202, the data link layer 204 and / or 206 physical layer processing step (for example, adding a header, data integrity, information, etc.).

根据一个实施例,响应于通过虚拟信道的数据报的接收,接收者中的流控制机制将发布流控制更新。 According to one embodiment, the virtual channel in response to a datagram reception, the recipient of the flow control mechanism to release the flow control update. 该更新可以是确认分组中的头部形式等等。 The updates can be confirmed in the form of packet header and the like. 在这样的实施例中,事务的流控制信用的返回不认为是意味着事务已经完成或事务已经实现系统可见(visibility)。 In such embodiments, the return flow control credit transactions do not think that means that a transaction is completed or transaction has been achieved system visibility (visibility). 使用存储器写入请求语义的消息信号中断(MSI)象任何其它存储器写入一样被处理。 Use semantic memory write request message signal interrupt (MSI) is written as like any other memory is processed. 如果随后的FC更新消息(来自接收者)指示了比最初指示的值更低的信用极限值,则发送者应当承认新的较低极限,并且提供一个消息错误。 If the subsequent FC update message (from the receiver) indicates a value lower than the initial indication of the credit limit, the sender should recognize the new lower limit, and a message error.

根据这里所描述的流控制机制,如果接收者接收到比分配的信用更多的信息(超过分配的信用),则接收者将向违规的发送者指示接收者溢出错误,并且对引起溢出的分组发起数据链路级别的重试请求。 The flow control mechanism described here, if the receiver receives more information (over allocation of credit) than the distribution of credit, the receiver will be the sender of the offending instruction receiver overflow error, and the cause overflow packet initiate the data link level retry the request.

在方框618中,在接收到流控制更新信息之后,与发送者中特定虚拟信道有关的流控制机制进而更新(多个)流控制寄存器以助于随后的流控制。 In block 618, after receiving flow control update information flow control mechanism with the sender in a particular virtual channel relating to further update (s) flow control registers to facilitate subsequent flow control.

上面已经介绍了体系结构元件和示例性操作细节,示出了用来传输流控制信息的示例性协议。 The above system has been described structural elements and operational details of an exemplary showing the flow control information is used to transmit an exemplary agreement. 根据一个示例性实施例,使用流控制分组在数据链路层204上传输流控制信息。 According to an exemplary embodiment, the use of flow control packets at the data link layer 204 transmission flow control information.

·流控制分组(FCP)根据一个实现,使用流控制分组(FCP)在设备之间传输保持上述寄存器所需的流控制信息。 · Flow control packet (FCP) According to one implementation, the use of flow control packet (FCP) transmission between devices required for holding the register flow control information. 参考图9,示出了示例性流控制分组。 Referring to Figure 9, there is shown an exemplary flow control packets. 根据一个实施例,流控制分组900包括用于具体虚拟信道的关于六个信用寄存器的状态的输送信息和2-DW头部格式,其中六个信用寄存器由接收事务层的流控制逻辑为每个VC保持。 According to one embodiment, the flow control packet 900 includes conveying information about the status of the six credit registers and 2-DW header format for a particular virtual channel, six credit registers received by the flow control logic for each transaction layer VC maintained.

根据本发明的教导的一个实施例,如图9所示有两种类型的FCP:初始FCP和更新FCP。 FCP according to one embodiment of the teachings of the present invention, shown in Figure 9. There are two types: Initial FCP and Update FCP. 如上所述,在初始化事务层时,发布初始FCP 902。 As described above, when initializing the transaction layer, release initial FCP 902. 在初始化事务层之后,更新FCP 904被用于更新寄存器中的信息。 After the initialization of the Transaction Layer, Update FCP 904 is used to update the information in the register.

在常规操作期间接收到初始FCP 902引起本地流控制机制的复位以及初始FCP 902的发送。 During normal operation of receiving the initial FCP 902 causing a reset local flow control mechanism and the transmission of the initial FCP 902. 初始FCP 902的内容包括为PH、PD、NPH、NPD、CPHL、CPHD和信道ID(例如,与应用FC信息相关联的虚拟信道)中的每个所通告的信用的至少一个子集。 Content Initial FCP 902 includes the PH, PD, NPH, NPD, CPHL, CPHD and channel ID (for example, the virtual channel information associated application FC) in each of at least a subset of the advertised credits.

更新FCP 904的格式与初始FCP 902的格式类似。 Update Format initial FCP 902 similar format FCP 904. 应当知道,尽管FC头部不包括其它事务层分组头部格式普遍具有的长度字段,但是分组的大小是明确的,因为没有与该分组相关的额外DW数据。 It should be appreciated that while the FC header length field does not include other transaction layer packet header format generally have, but the packet size is ambiguous because there is no additional DW data associated with the packet.

错误转发与传统的错误转发机制不同,EGIO体系结构依靠附加到被识别为由于如下描述的多个原因而且具有的缺陷的(多个)数据报上的尾部信息。 Error forwarding with different conventional error forwarding mechanisms, EGIO architecture relies attached to a number of reasons to be identified as described below and having a defect (s) on the packet trailer information. 根据一个示例性实现,事务层202使用了多种公知错误检测技术中的任何一种,例如循环冗余校验(CRC)错误控制等等。 According to one example implementation, transaction layer 202 using a variety of well known error detection technique in any one of e.g., cyclic redundancy check (CRC) error control and the like.

根据一个实现,为了有助于错误转发特征,EGIO体系结构使用了“尾部”,其附加到携带已知坏数据的TLP上。 According to one implementation, in order to facilitate error forwarding features, EGIO architecture uses a "tail", which is attached to the carrying known bad data TLP. 可能使用尾部错误转发的情况示例包括:示例#1:来自主存储器的读取遇到无法纠正的ECC错误示例#2:向主存储器的PCI写入的奇偶错误示例#3:内部数据缓冲器或高速缓存中的数据完整性错误根据一个示例性实现,错误转发仅用于读取完成数据或写入数据。 Examples of possible error conditions using the tail forward include: Example # 1: Read from the main memory has encountered an uncorrectable ECC error Example # 2: Parity Error Example main memory is written to the PCI # 3: The internal data buffer or cache data integrity errors in accordance with one exemplary implementation, error forwarding is only used for data read or write data. 即,对于与数据报相关的管理开销中发生错误的情形,例如头部中的错误(例如请求阶段、地址/命令等等),一般不使用错误转发。 That is, the data packets associated management overhead in the wrong situations such as the head of an error (for example, the request phase, the address / command, etc.) occurs, generally do not use the wrong transponder. 如这里所使用的,具有头部错误的请求/完成通常不能被转发,这是由于不能确定地识别真实目的地,并且因此该错误转发可能引起直接或间接影响,例如数据损坏、系统故障等等。 As used herein, a head having a bad request / complete normally can not be forwarded, which is due to identify the true destination can not be determined, and thus the error forwarding may cause directly or indirectly affect, for example data corruption, system failures, etc. . 根据一个实施例,错误转发用于传播错误通过系统以及系统诊断。 According to one embodiment, error forwarding is used to propagate through the system errors and system diagnostics. 错误转发不使用数据链路层重试,因此只有在EGIO链路112上出现如TLP错误检测机制(例如,循环冗余校验(CRC)等等)所确定的发送错误时,才重试以尾部结束的TLP。 Error Forwarding does not use the data link layer retries, so only the EGIO link 112 appears as TLP error detection mechanisms (for example, a cyclic redundancy check (CRC), etc.) as determined by a transmission error, it retries to the tail end of the TLP. 因此尾部可能最终引起请求的发起者重新发布它(在上述的事务层)或者采取某个其它的动作。 Therefore, the tail may ultimately cause the originator of the request to re-publish it (in the above transaction layer) or take some other action.

如这里所使用的,所有EGIO接收者(例如,位于EGIO接口106中)都能够处理以尾部结束的TLP。 As used herein, all EGIO receivers (e.g., located in the EGIO interface 106) are able to deal with the tail end of the TLP. 在发送者中对加入尾部的支持是可选的(因而与老式设备兼容)。 In the rear of the sender added support is optional (and therefore compatible with older devices). 交换器108对尾部和TLP的其余部分一起进行路由。 Exchange 108 the rest of the tail and TLP be routed together. 具有对等(peer)路由支持的根复合体104一般会一起路由尾部和TLP的其余部分,但不是必需如此。 With a peer (peer) routing support root complex 104 generally along the route of the rest of the tail and TLP, but not necessarily so. 错误转发一般适用于写入请求(公布的或非公布的)或读取完成中的数据。 Error Forwarding generally applicable to a write request (published or non-published) or read data is completed in. 发送者知道的含有坏数据的TLP应当以尾部结束。 Sender knows the TLP contains bad data should end with the tail.

根据一个示例性实现,尾部由2DW组成,其中字节[7:5]是全零(例如,000),并且比特[4:1]是全一(例如,1111),而预留所有其它比特。 According to an exemplary implementation, the tail from the 2DW composition, wherein bytes [7: 5] are all zeroes (e.g., 000), and bits [4: 1] is a whole (e.g., 1111), while all other bits reserved . EGIO接收者会认为以尾部结束的TLP中的所有数据都是损坏的。 EGIO receiver will consider in the tail end of the TLP all the data is corrupted. 如果应用错误转发,则接收者将指定TLP的所有数据标记为坏(“中毒”)。 If the application error forwarding, the receiver will specify all data TLP is marked as bad ("poisoned"). 在事务层中,分析器(parser)一般会分析到整个TLP的末端并马上校验随后的数据,以了解数据是否结束。 In the transaction layer, the analyzer (parser) general analyzes to the end of the entire TLP and check immediately subsequent data, to see whether the data end.

数据链路层204如上所述,图2的数据链路层204充当事务层202和物理层206之间的中间级(stage)。 Data Link Layer The data link layer 204 as described above, 204 of FIG. 2 serves as an intermediate-level transaction layer 202 and physical layer 206 between the (stage). 数据链路层204的主要责任是提供用于通过EGIO链路112在两个组件之间交换事务层分组(TLP)的可靠机制。 The main responsibility of the data link layer 204 is to provide a transaction layer packet (TLP) of the EGIO link 112 through a reliable mechanism to exchange between the two components. 数据链路层204的发送方接收由事务层202装配的TLP、应用分组序列标识符(例如,标识号码)、计算并应用错误检测代码(例如,CRC代码)并且向物理层206递交修改的TLP,用于通过挑选的一条或多条在EGIO链路112的带宽中建立的虚拟信道而进行传输。 The data link layer of the transmitting side is received by the transaction layer 204 of assembly 202 TLP, application packet sequence identifier (e.g., identification number), calculates and applies an error detection code (e.g., CRC code) and submitted to the physical layer 206 of the modified TLP used by selecting one or more of the EGIO link 112 to establish a virtual bandwidth channel and transmitted.

接收数据链路层204负责校验所接收TLP的完整性(例如,使用CRC机制等等),并且负责向事务层204递交完整性校验是肯定的那些TLP,以用于在转发到设备核心之前进行分解。 204 receives the data link layer is responsible for verification of the integrity of the TLP received (for example, using CRC mechanisms, etc.), and is responsible to check the integrity of the transaction layer 204 is sure to submit those TLP, for forwarding to the device core before decomposition. 由数据链路层204提供的服务通常包括数据交换、错误检测与重试、初始化与电源管理服务,以及数据链路层内部通信服务。 Service 204 provided by the data link layer typically comprises a data exchange, error detection and retry, initialization and power management services, and internal data link layer communication services. 基于前述分类提供的每种服务列举如下:数据交换服务-从发送事务层接受用于发送的TLPi.接受通过链路从物理层接收的TLP,并且将它们传输到接收事务层错误检测&amp;重试-TLP序列号码与CRC生成-已发送TLP存储器,用于数据链路层重试-数据完整性校验-确认以及重试DLLP-记录机制和错误报告的错误指示i.链路Ack超时定时器初始化与电源管理服务-跟踪链路状态并能够传输有效/复位/断开连接状态到事务层数据链路层内部通信服务-用于包括错误检测以及重试的链路管理功能-在两个直接相连的组件的数据链路层之间进行传输-没有暴露给事务层如在EGIO接口106中所使用的,数据链路层204对于事务层202表现为具有不同延迟的信息导管(conduit)。 Each service provided based on the aforementioned classification are listed below: Data Exchange Services - receiving from a transmitting transaction layer for transmission through TLPi receiving link received from the physical layer TLP, and transmits them to the Receive Transaction Layer Error Detection & amp; weight. -TLP test sequence number and CRC generation - has been sent TLP memory for the data link layer retries - Data integrity check - Verify and retry DLLP- recording mechanism and error reporting error indication i link Ack timeout timer Initialization and power management services - tracking link status and the ability to transmit efficiently / reset / disconnected data link layer to the transaction layer internal communication services - to include error detection and retry link management function - in two transmission between components directly connected to the data link layer - the transaction layer as EGIO interface 106 used in the data link layer 204 is not exposed to the performance of the transaction layer 202 to have different delay information conduit (conduit). 馈送到发送数据链路层的所有信息在较晚的时间处将出现在接收数据链路层的输出端。 Fed to transmit data link layer all the information at a later time will appear at the output of the receiving data link layer. 延迟将取决于许多因素,包括管道延迟、链路112的宽度和操作频率、通过介质的通信信号的发送、以及由数据链路层重试引起的延时。 Delay will depend on many factors, including pipeline delay, link width and operating frequency 112 by transmitting a communication signal medium, and the delay is determined by the data link layer retry caused. 由于这些延时,发送数据链路层可以向发送事务层202施加反压力(backpressure),并且接收数据链路层将有效信息的存在和缺失传输到接收事务层202。 Because of these delays, the transmission data link layer may be applied to the transmission of the transaction layer 202 backpressure (backpressure), and receives the data link layer to the presence and absence of effective information is transmitted to the receiving transaction layer 202.

根据一个实现,数据链路层204跟踪EGIO链路112的状态。 According to one implementation, the data link layer 204 to track the status of EGIO link 112. 在这方面,DLL 204与事务202和物理层206传输链路状态,并且通过物理层206执行链路管理。 In this regard, DLL 204 and 202 and physical layer 206 transaction transmission link status, and performs Link Management through the physical layer 206. 根据一个实现,数据链路层含有链路控制与管理状态机来执行这样的管理任务,参考图11图示了所述状态机的一个示例。 According to one implementation, the data link layer contains link control and management state machine to perform such administrative tasks, an example with reference to FIG. 11 illustrates the state machine. 根据图11的示例性实现,链路控制与管理状态机的状态1100定义如下:示例性DLL链路状态·LinkDown(链路停用)(LD)-物理层报告链路是不可操作的,或者没有连接端口·LinkInit(链路初始化)(LI)-物理层报告链路是可操作的并且正在初始化·LinkActive(链路有效)(LA)-常规操作模式·LinkActDefer(链路动作延期)(LAD)-常规操作中断,物理层试图恢复每个状态的对应管理规则:·LinkDown(LD)跟随在组件复位之后的初始状态在进入LD后-将所有数据链路层状态信息复位成缺省值在LD中时-不和事务层或物理层交换TLP信息-不和物理层交换DLLP信息-不产生或接受DLLP退出转入LI,如果:-来自事务层的指示是链路没有被SW禁用·LinkInit(LI)在LI中时-不和事务层或物理层交换TLP信息-不和物理层交换DLLP信息 1100 defined by the state of an exemplary implementation, link control and management state machine of FIG. 11 is as follows: an exemplary DLL link status · LinkDown (link disabled) (LD) - Physical layer reports the link is inoperable, or No connection port · LinkInit (link initialization) (LI) - Report of the physical layer link is operational and is initialized · LinkActive (link valid) (LA) - General Operating mode · LinkActDefer (link action extension) (LAD ) - General operation is interrupted, trying to recover the corresponding physical layer management rules for each state: · LinkDown (LD) following the initial state after module reset after entering LD - all the data link layer state information is reset to the default values LD when - not the physical layer and transaction layer or exchange TLP information - not physical layer switching DLLP information - does not produce or accept DLLP withdraw into LI, if: - the instruction from the transaction layer is a link has not been disabled · LinkInit SW (LI) LI when in - without the physical layer and transaction layer or exchange TLP information - not with physical layer information exchange DLLP

-不产生或接受DLLP退出转入LA,如果:-来自物理层的指示是链路训练(training)成功退出转入LD,如果:-来自物理层的指示是链路训练(training)失败·LinkActive(LA)在LinkAcfve中时:-和事务层与物理层交换TLP信息-和物理层交换DLLP信息-产生并接受DLLP。 - Do not generate or accept DLLP withdraw into LA, if: - the instruction from the physical layer is to link training (training) successful exit into LD, if: - the instruction from the physical layer is to link training (training) fail · LinkActive (LA) in LinkAcfve when: - and the transaction layer and the physical layer exchange TLP information - and the physical layer exchange DLLP information - generate and accept DLLP.

退出进入LinkActDefer,如果:-来自数据链路层重试管理机制的指示是需要链路的重新训练,或者如果物理层报告重新训练正在进行中。 Exit enter LinkActDefer, if: - the instruction from the data link layer retries management mechanism is re-training needs of the link, or if the physical layer retrain progress report.

·LinkActDefer(LAD)在LinkActDefer中时-不和事务层或物理层交换TLP信息-不和物理层交换DLLP信息-不产生或接受DLLP退出进入LinkActive,如果:-来自物理层的指示是重新训练成功退出进入LinkDown,如果:-来自物理层的指示是重新训练失败数据完整性管理如这里所使用的,数据链路层分组(DLLP)被用于支持EGIO链路数据完整性机制。 · LinkActDefer (LAD) LinkActDefer when in - without the physical layer and transaction layer or exchange TLP information - not physical layer switching DLLP information - does not produce or accept DLLP exit into the LinkActive, if: - the instruction from the physical layer is re-training success exit enter LinkDown, if: - the instruction from the physical layer is re-training as fail data integrity management, data link layer packet (DLLP) as used herein are used to support EGIO link data integrity mechanisms. 在这方面,根据一个实现,EGIO体系结构规定了下列DLLP来支持链路完整性管理:·Ack DLLP:TLP序列号码确认-用于指示成功接收了某些数量的TLP In this regard, according to one implementation, EGIO architecture provides the following DLLP to support link integrity management: · Ack DLLP: TLP Sequence Number Validation - used to indicate the successful reception of a certain number of TLP

·Nak DLLP:TLP序列号码否定确认-用于指示数据链路层重试·Ack超时DLLP:指示最近发送的序列号码-用于检测某些形式的TLP丢失如上所述,事务层202向数据链路层204提供TLP边界信息,使得DLL 204能够将序列号码和循环冗余校验(CRC)错误检测应用于TLP。 · Nak DLLP: TLP Sequence number negative acknowledgment - is used to indicate the data link layer retries · Ack Timeout DLLP: indicates the sequence number of the last sent - TLP used to detect certain forms of loss as described above, the transaction layer 202 to the data link channel layer 204 provides TLP boundary information, so that the DLL 204 can be serial number and a cyclic redundancy check (CRC) error detection applied TLP. 根据一个示例性实现,接收数据链路层通过校验序列号码、CRC代码和来自接收物理层的任何错误指示来验证接收的TLP。 According to an exemplary implementation, by checking the received data link layer sequence number, CRC code and any error indications from the physical layer of the receiver to verify the received TLP. 如果TLP中有错误,则使用数据链路层重试来恢复。 TLP if there is an error, then use the data link layer retries to recover. 尽管这里的描述使用了CRC,本领域技术人员应当理解也可以使用其它形式的错误检测,例如数据报内容的哈希散列(hash)等等。 Although the description herein using the CRC, the skilled person will understand that also other forms of error detection may be used, e.g., datagram content hashes (hash) and the like.

CRC、序列号码以及重试管理(发送者)在概念“计数器”和“标志”方面,以下描述了用于确定TLP、CRC和序列号码以支持数据链路层重试的机制:CRC与序列号码规则(发送者)·使用下列8比特计数器:o TRANS_SEQ-存储应用于正在准备发送的TLP的序列号码.在LinkDown状态下设定为全'0'.在每个TLP发送后,增加1.当全'1'时,增加引起翻转使得全'0'.Nak DLLP的接收引起值被重新设定为Nak DLLP中指示的序列号码o ACKD_SEQ-存储在最近接收的链路到链路确认DLLP中确认的序列号码。 CRC, serial number and retry management (sender) in the concept of "counter" and "flag", the following description of a method for determining TLP, CRC and serial number of mechanisms to support data link layer retries: CRC and sequence number rules (sender) - 8-bit counter using the following:.. o TRANS_SEQ- storage applies TLP serial number are preparing to send in LinkDown state is set for the whole '0' after each TLP transmission increases 1. When Full '1', the increase caused by flipping makes the whole '0'.Nak DLLP received cause value is reset Nak DLLP indicated in the serial number o ACKD_SEQ- stored in the most recently received link to link confirmation DLLP confirmed The sequence number.

.在LinkDown状态下设定为全'1'·每个TLP被分配8比特序列号码o计数器TRANS_SEQ存储这个号码o如果TRANS_SEQ等于(ACKD_SEQ-1)模256,则发送者一般不会发送另一TLP,直到Ack DLLP更新ACKD_SEQ,使得条件(TRANS_SEQ==ACKD_SEQ-1)模256不再正确。 Set in the LinkDown state for the whole '1' • Each TLP is assigned an 8-bit serial number o counter TRANS_SEQ store the number o If TRANS_SEQ equal (ACKD_SEQ-1) module 256, the sender does not send another general TLP until Ack DLLP update ACKD_SEQ, making conditions (TRANS_SEQ == ACKD_SEQ-1) module 256 is no longer correct.

·TRANS_SEQ应用于TLP,通过:o为TLP预先准备(prependirg)单个字节值o为TLP预先准备单个预留字节·使用下述算法为TLP计算32b CRC,并将其附加在TLP末端o使用的多项式是0x04C11DB7-与以太网使用的相同的CRC-32o计算过程是:1)CRC-32计算的初始值是通过为序列号码预先准备24个'0'而形成的DW2)以从包括头部的字节0的DW到TLP的最后DW的顺序,使用来自事务层的TLP的每个DW而继续CRC计算3)取来自计算的比特序列的补码,结果是TLP CRC4)CRC DW附加在TLP的末端·已发送TLP的拷贝一般会存储在数据链路层重试缓冲器中·当从其它设备接收到Ack DLLP时:o ACKD_SEQ装入在DLLP中指定的值o重试缓冲器清除序列号码在下述范围内的TLP:.从ACKD_SEQ的先前值+1.到ACKD_SEQ的新值·当从链路上的其它组件接收到Nak DLLP时:o如果正在向物理层传输TLP,则继续该传输直到该TLP的传输完成o不从事务层获得另外的TLP,直到完成了下述步骤o重试缓冲器清除序列号码在下述范围内的TLP:.从ACKD_SEQ的先前值+1.到在Nak DLLP的Nak序列号码字段中指定的值o重试缓冲器中所有剩余的TLP都重新提交到物理层,用于以原始顺序重新发送.注意:这将包括序列号码在下述范围内的所有TLP: · TRANS_SEQ applied TLP, through: o prepared in advance for the TLP (prependirg) single byte value for the TLP o prepared in advance to reserve a single byte * TLP calculated using the following algorithm 32b CRC, and attach it at the end o the use of TLP The polynomial is the same CRC-32o 0x04C11DB7- calculation Ethernet using: 1) CRC-32 calculation is the initial value of the sequence numbers prepared in advance by 24 '0' formed DW2) to the head portion comprises byte DW 0 to DW's order last TLP, using each DW TLP from the transaction layer and continue CRC calculation 3) complemented bit sequence from the calculation, the result is TLP CRC4) CRC DW attached TLP · end sent a copy of TLP typically stored in the data link layer retry buffer • When receiving from other devices to Ack DLLP: o ACKD_SEQ DLLP load values specified in the retry buffer clearing o Sequence Number In the following range of TLP :. from the previous value of +1 to ACKD_SEQ ACKD_SEQ new value · When receiving from the other components on the link to Nak DLLP: o If you are to the physical layer transmission TLP, then proceed with the transfer until completion of transmitting the TLP o not get another TLP from the transaction layer, complete the following steps until o retry buffer clear sequence number within the following range of TLP :. ACKD_SEQ previous value from +1. to the Nak DLLP of Nak Sequence Number value specified in the field o retry buffer all remaining TLP are resubmitted to the physical layer for the original sequence resend Note: This will include all the TLP serial number within the following range:

o在Nak DLLP的Nak序列号码字段中指定的值+1o TRANS_SEQ的值-1.如果在重试缓冲器中没有剩余的TLP,则Nak DLLP错误o根据错误跟踪和记录部分,一般会报告错误的Nak DLLPo发送者不需要其它的动作CRC与序列号码(接收者)类似地,在概念“计数器”和“标志”方面,以下描述了用于确定TLP、CRC和序列号码以支持数据链路层重试的机制:·使用下列8比特计数器:o NEXT_RCV_SEQ-为下一个TLP存储期望的序列号码.在LinkDown状态下设定为全'0'.对于接受的每个TLP,增加1,或者当通过接受TLP而清除DLLR_IN_PROGRESS标志(下文描述)时.每次接收到链路层DLLP并且DLLR_IN_PROGRESS标志被清除时,装入值(Trans.Seq.Num+1)o如果NEXT_RCV_SEQ的值与已接收的TLP或Ack超时DLLP指定的值不同,则指示在发送者和接收者之间的序列号码同步丢失;在这种情况下:·如果设定了DLLR_IN_PROGRESS标志,则o复位DLLR_IN_PROGRESS标志o发送“发送坏DLLR DLLP”错误到错误记录/跟踪o注意:这指示错误地发送了DLLR DLLP(Nak)·如果没有设定DLLR_IN_PROGRESS标志,则o设定DLLR_IN_PROGRESS标志并且发起Nak DLLPo注意:这指示TLP丢失 o value specified in the Nak Nak DLLP sequence number field + 1o TRANS_SEQ the value -1 if there are no remaining TLP, the Nak DLLP o error according to the error tracking and recording section, generally reports an error in the retry buffer Nak DLLPo sender does not require further actions CRC and Sequence Number (receiver) Similarly, the concept of "counters" and "flags", the following description for determining TLP, CRC and sequence numbers to support the weight of the data link layer Mechanism test: • Use the following 8-bit counter: o NEXT_RCV_SEQ- TLP storage for the next expected sequence number is set to all 0's in the LinkDown state for each TLP accepted, increased by 1, or when by receiving. When TLP cleared DLLR_IN_PROGRESS flag (described below) when each time receiving link layer DLLP and DLLR_IN_PROGRESS flag is cleared, load value (Trans.Seq.Num + 1) o If the value NEXT_RCV_SEQ and received TLP or Ack Timeout DLLP specified values are different, it indicates that between the sender and receiver serial number synchronization is lost; in this case: If set DLLR_IN_PROGRESS flag is reset DLLR_IN_PROGRESS flag o o Send 'to send bad DLLR DLLP " error to error logging / tracing o NOTE: This indicates erroneously transmitted DLLR DLLP (Nak) · If no DLLR_IN_PROGRESS flag is set o DLLR_IN_PROGRESS flag and initiate Nak DLLPo NOTE: This indicates TLP loss

·使用下述3比特计数器:o DLLRR_COUNT-对在特定时间段内发布的DLLR DLLP的次数进行计数.在LinkDown状态下设定为b'100.对于发布的每个Nak DLLP,增加1·当计数达到b'100时:o链路控制状态机从LinkActive移动到LinkActDefero DLLRR_COUNT随后被复位为b'000·如果DLLRR_COUNT不等于b'000,每256个符号时间减1o即,在b'000饱和·使用下述标志:o DLLR_IN_PROGESS·下面描述设定/清除条件·当设定了DLLR_IN_PROGESS时,丢弃所有已接收的TLP(直到接收到由DLLR_DLLP指示的TLP)·当DLLR_IN_PROGESS是清空的时,如下所述校验已接收的TLP·对于将要接受的TLP,下述条件一般应当为真:o已接收的TLP序列号码等于NEXT_RCV_SEQo物理层没有指示在TLP接收过程中的任何错误o TLP CRC校验不指示错误·当接受了TLP时:o TLP的事务层部分被转发到接收事务层o如果设定,则清空DLLR_IN_PROGESS标志o增加NEXT_RCV_SEQ·当没有接受TLP时:o设定DLLR_IN_PROGESS标志 Use the following three-bit counter:.. O DLLRR_COUNT- DLLR DLLP number of times in a given period of time to count is set to release in LinkDown b'100 state for each Nak DLLP released, increasing the 1. When the count b'100 reached when: o link control state machine is then reset from LinkActive move to LinkActDefero DLLRR_COUNT to b'000 · If DLLRR_COUNT not equal b'000, each 256 symbol time minus 1o That, in b'000 saturation Use The following signs: o DLLR_IN_PROGESS · The following description Set / Clear Conditions • When setting up DLLR_IN_PROGESS, discard all received TLP (TLP until it receives instructions from the DLLR_DLLP) • When DLLR_IN_PROGESS is cleared when, as the school It received TLP · test will be accepted for TLP, the following conditions should generally true: TLP serial number o received equal NEXT_RCV_SEQo physical layer does not indicate any error in the TLP reception process o TLP CRC check does not indicate an error · When accepting the TLP: o Transaction Layer part TLP is forwarded to the receiving transaction layer o If set, the empty flag DLLR_IN_PROGESS o increase NEXT_RCV_SEQ · When there is no accepted TLP: o set DLLR_IN_PROGESS flag

o发送Nak DLLP·Ack/Nak序列号码字段一般会包含值(NEXT_RCV_SEQ-1)·Nak类型(NT)字段一般会指示Nak的原因o b'00-由物理层识别的接收错误o b'01-TLP CRC校验失败o b'10-序列号码不正确o b'11-由物理层识别的成帧错误·接收者一般不会允许从接收TLP的CRC到发送Nak的时间超过1023个符号时间,如从组件的端口所测量的那样。 o Send Nak DLLP · Ack / Nak Sequence Number field generally contains the value (NEXT_RCV_SEQ-1) · Nak type (NT) field generally indicates the reason Nak o b'00- reception errors identified by the physical layer o b'01- TLP CRC check fails o b'10- serial number is incorrect o b'11- identified by the physical layer framing errors · the recipient generally does not allow the CRC from the received TLP Nak time to send more than 1023 symbols time, As port assembly measured from.

o注意:没有增加NEXT_RCV_SEQ·如果接收数据链路层没有接收到在其后的512符号时间内跟随着NakDLLP的期望TLP,则重复Nak DLLP。 o Note: No increase NEXT_RCV_SEQ · If the received data link layer is not received within a further 512 symbols time followed NakDLLP expectations TLP, then repeat Nak DLLP.

o如果经过四次尝试后仍然没有接收到期望的TLP,则接收者将:.进入LinkActDefer状态,并启动由物理层进行的链路重新训练.将主要错误的发生指示给错误跟踪与记录·当下列条件为真时,一般会发送数据链路层确认DLLP:o数据链路控制与管理状态机处于LinkActive状态o已经接受了TLP,但还没有通过发送确认DLLP进行确认o从最后的确认DLLP起已经经过了超过512个符号时间·可以比所需要的更频繁地发送数据链路层确认DLLP·数据链路层确认DLLP在Ack序列Num字段内规定值(NEXT_RCV_SEQ-1)Ack超时机制考虑TLP在链路112上被损坏使得接收者不能检测到TLP的存在的情况。 o If after four attempts still have not received the expected TLP, then the recipient will: enter LinkActDefer state, and to initiate a link from the physical layer re-training will be major error occurrence indication to the wrong track when recording *. The following conditions are true, usually sending data link layer confirm DLLP: o data link control and management state machine is in state o LinkActive has accepted the TLP, but have not yet confirmed the final confirmation from DLLP o by sending an acknowledgment from DLLP have gone through more than 512 symbols time · can send more frequent than necessary to confirm the data link layer, data link layer confirm DLLP · DLLP provisions in the Ack Sequence Num field value (NEXT_RCV_SEQ-1) Ack timeouts consider TLP in link 112 is damaged so that the receiver can not detect the presence of the TLP. 当发送随后的TLP时将检测到丢失的TLP,因为TLP序列号码与接收者处的期望序列号码不匹配。 When sending subsequent TLP detected lost TLP, because the expected sequence number and the recipient of the TLP serial number does not match. 然而发送数据链路层204通常不能限定下一TLP从发送传输层到在发送数据链路层204上面出现的时间。 But sending data link layer 204 typically can not limit the time of the next TLP from the transport layer to send the transmission data link layer 204 appears above. Ack超时机制允许发送者限定接收者所需的检测丢失TLP的时间。 Ack Timeout mechanism allows the sender to the recipient needed to detect the loss of qualified TLP time.

Ack超时机制规则.如果发送重试缓冲器含有没有接收到Ack DLLP的TLP,并且如果在超过1024个符号时间的时间段内没有发送TLP或链路DLLP,则一般会发送Ack超时DLLP。 Ack timeout rule mechanism. If you send retry buffer containing not received Ack DLLP the TLP, and if not sent TLP or link DLLP in more than 1024 symbols time period, it is generally sends Ack timeout DLLP.

.在发送Ack超时DLLP之后,数据链路层一般不会传送任何TLP到物理层用于发送,直到从链路的另一方的组件接收到确认DLLP。 After sending Ack Timeout DLLP, the data link layer typically does not send any TLP to the physical layer for transmission, from the other component until it receives an acknowledgment link DLLP.

o如果在超过1023个符号时间的时间段内没有接收到确认DLLP,则再次发送Ack超时DLLP,在第四次连续发送Ack超时DLLP之后的1024个符号时间内仍没有接收到确认DLLP,进入LinkActDefer状态并且启动由物理层进行的链路保持.将主要错误的发生指示给错误跟踪与记录。 o If no acknowledgment is received in more than 1023 symbols DLLP time period, then resend Ack timeout DLLP, sending the fourth consecutive time in the 1024 symbol Ack timeout after DLLP still not received confirmation DLLP, enter LinkActDefer state and activated by the physical layer of the link remains. The main error occurrence indication to the wrong track and record.

上文已经介绍了数据链路层204的数据完整性机制的体系结构上的元件以及协议元件,参考图7,其中根据一个示例性实施例示出了数据完整性机制的示例性实现。 As already described elements and protocol element architecture data link layer data integrity mechanisms 204 on 7, which according to an exemplary embodiment shows an exemplary data integrity mechanisms.

图7是根据本发明的一个示例性实施例的用于在EGIO体系结构中监视数据完整性的示例性方法的流程图。 7 is a flowchart EGIO architecture to monitor the data integrity of an exemplary method according to an exemplary embodiment of the present invention. 根据图7所图示的示例性实现,方法以方框702开始,其中在EGIO元件的EGIO接口106处通过虚拟信道接收数据报。 According to the illustrated exemplary implementation of FIG. 7, the method to start block 702, which receives data packets in the interface EGIO EGIO element 106 through the virtual channel. 如上所述,数据报在提升进入数据链路层204之前通过物理链路层206接收。 As described above, the data reported before ascending into the data link layer 204 is received through the physical link layer 206. 根据某些实施例,物理层206确定所接收的数据报是否符合分组成帧(framing)需求等。 According to some cases, the implementation of the physical layer 206 determines whether the received data packets conform packet framing (framing) demand. 在某些实施例中,丢弃未能满足这样的成帧需求的数据报,而不会提升或由数据链路层204的数据完整性机制分析。 In certain embodiments, the discarded failed to meet this requirement framing datagrams, and not improve or analyze the data integrity mechanism of the data link layer 204. 如果证实了成帧,物理层从数据报剥去成帧边界以显露数据链路层分组,其被提升到数据链路层。 If confirmed by the framing, the physical layer framing boundary stripped from the datagram to reveal the data link layer packet, which is elevated to the data link layer.

在方框704中,在从物理层206接收到数据报之后,在数据链路层204中证实数据链路层分组的完整性。 In block 704, after receiving data from the physical layer 206 to report, confirm the integrity of the data link layer packet in a data link layer 204. 如上所述,数据链路层204的数据完整性机制使用序列号码、CRC信息等等中的一个或多个来证实包括TLLP和其他事物的DLLP中的信息正确。 One or more as described above, the data link layer data integrity mechanisms using a sequence number 204, CRC information, etc. The confirmed include TLLP and other things DLLP the information is correct.

如果在方框704中数据链路层204识别了所接收DLLP的完整性中的缺陷,则数据链路层204调用上面提到的错误处理机制实例。 If in block 704 the data link layer 204 identifies the received DLLP integrity defects, the data link layer 204 calls the error handling mechanism mentioned above examples.

如果在方框704中,数据链路层204证实了所接收DLLP的完整性,则在方框708中所接收DLLP的至少一个子集被提升到事务层202。 If at block 704, the data link layer 204 confirmed DLLP received integrity, in block 708 DLLP received at least a subset of the 202 has been elevated to the transaction layer. 根据一个示例性实现,剥去针对数据链路层的信息(例如,头部、注脚(footer)等)以显露TLLP,其被传送到事务层用于进一步的处理。 According to an exemplary implementation, the data link layer stripped for information (e.g., header, footer (footer), etc.) to reveal TLLP, which is transferred to the transaction layer for further processing.

物理层206继续参考图2,示出了物理层206。 Physical Layer 206 With continued reference to FIG. 2, there is shown a physical layer 206. 如这里所使用的,物理层206使事务202和数据链路204与用于链路数据相互交换的信令技术相隔离。 As used herein, the physical layer 206 so that the transaction data 202 and data link 204 links exchange signaling techniques are used to isolate. 根据图2所图示的示例性实现,物理层划分为逻辑208和物理210功能子块。 According to the illustrated exemplary implementation of FIG. 2, the physical layer is divided into the logical 208 and physical 210 functional sub-blocks.

如这里所使用的,逻辑子块208负责物理层206的“数字”功能。 As used herein, the logical sub-block 206 in the physical layer 208 is responsible for the "digital" function. 在这方面,逻辑子块204具有两个主要划分:发送部分,准备输出信息用于由物理子块210进行发送;以及接收者部分,用于在将所接收信息传送到链路层204之前识别并准备该信息。 In this regard, the logical sub-block 204 has two main partition: a transmission section for outputting information prepared by the physical sub-block 210 for transmission; and a receiver portion for transmitting the received information before the link layer 204 identifies and the preparation of the information. 逻辑子块208和物理子块210通过状态与控制寄存器接口协调端口状态。 Logical sub-block 208 and physical sub-block 210 by state and port state control register interface coordination. 由逻辑子块208指导物理层206的控制与管理功能。 The logical sub-block 208 to guide the physical layer 206 control and management functions.

根据一个示例性实现,EGIO体系结构使用8b/10b发送代码。 According to one example implementation, EGIO architecture uses 8b / 10b transmission code. 使用该方案,8比特字符被视为3比特和5比特,所述3比特和5比特各自映射到4比特代码组和6比特代码组。 With this scheme, 8-bit characters are treated as 3-bit and 5 bits, the 3-bit and 5 bits are each mapped to a 4-bit code group and a 6-bit code groups. 这些代码组被连接以形成10比特符号。 These code groups are connected to form a 10-bit symbols. EGIO体系结构使用的8b/10b编码方案提供了专用符号,其与用来表示字符的数据符号完全不同。 8b / 10b encoding scheme used by EGIO architecture provides a special symbol, which is used to represent data symbols and characters are completely different. 这些专用符号用于下面的多种链路管理机制。 These special symbols are used for a variety of link management mechanism below. 专用符号还用于成帧DLLP和TLP,使用完全不同的专用符号允许快速便捷地区分这两类分组。 DLLP special symbol is also used to framing and TLP, use completely different special symbol allows quick and easy to distinguish these two types of packets.

物理子块210包括发送者和接收者。 Physical sub-block 210 includes a sender and a receiver. 逻辑子块208向发送者供应符号,发送者串行化这些符号并将其发送到链路112。 Logical sub-block 208 supplies the symbol to the sender, the sender of the serial symbols and sends it to the link 112. 链路112向接收者供应串行化符号。 112 serial link supply of symbols to the recipient. 接收者将所接收信号转换为比特流,比特流被解串行化,并且连同从输入串行流中恢复的符号时钟一起被供应道逻辑子块208。 The recipient of the received signal into a bit stream, the bit stream is de-serialized, and together with the recovery from the input serial stream is supplied together with the symbol clock channel logical sub-block 208. 应当理解,如这里所使用的,EGIO链路112可以代表多种通信介质中的任何一种,包括:电通信链路、光通信链路、RF通信链路、红外线通信链路、无线通信链路等等。 It should be understood that, as used herein, EGIO link 112 may represent a plurality of communication media either, comprising: an electrical communication link, an optical communication link, RF communication link, infrared communication link, a wireless communication link so on the road. 在这方面,包括物理层206的物理子块210的(多个)发送者和/或(多个)接收者中的每一个都适合于一种或多种上述通信链路。 In this regard, including the physical layer 206 physical sub-block 210 (s) transmit and / or (s) of each receiver adapted to one or more of the communication link.

示例性通信代理图8示出了含有与本发明相关联的特征的至少一个子集的示例性通信代理的方框图。 Exemplary communication agent Figure 8 shows a block diagram of an exemplary communication agent containing at least a subset of the present invention associated with the features. 根据本发明的一个示例性实现,根据图8所图示的示例性实现,所描述的通信代理800包括控制逻辑802、EGIO通信引擎804、数据结构的存储器空间806、以及可选的一个或多个应用808。 According to an exemplary implementation of the present invention, illustrated in FIG. 8 according to an exemplary implementation, the communication agent 800 includes the described control logic 802, EGIO communication engine 804, memory space for data structures 806, and optionally one or more 808 apps.

如这里所使用的,控制逻辑802向EGIO通信引擎804的一个或多个元件中的每个提供处理资源以选择性地实现本发明的一个或多个方面。 As used herein, control logic 802 provides processing resources to selectively implement a more aspects of the present invention or the EGIO communication engine 804 or a plurality of elements each. 在这个方面,控制逻辑802被规定为代表微处理器、微控制器、有限状态机、可变成逻辑器件、现场可编程门阵列、或当执行时使控制逻辑实现上述之一功能的内容中的一个或多个。 In this respect, the control logic 802 is defined as the representative of a microprocessor, a microcontroller, a finite state machine, can be turned into a logic devices, field programmable gate arrays, or the control logic to achieve when performing one of the functions of the content above One or more.

所描述的EGIO通信引擎804包括事务层接口202、数据链路层接口204、以及包括逻辑子块208和物理子块210以连接通信代理800和EGIO链路112的物理层接口206中的一个或多个。 EGIO communication engine 804 described interface 202 includes a transaction layer, data link layer interface 204, and includes a logical sub-block 208 and physical sub-block 210 to connect the communication agent 800 and EGIO link 112 of the physical layer interface 206 to one or multiple. 如这里所使用的,EGIO通信引擎804的元件执行与上述的功能相同或类似的功能。 As used herein, EGIO communication engine 804 perform the above-described elements function in the same or similar functions.

根据图8所图示的示例性实现,所描述的通信代理800包括数据结构806。 According to the illustrated exemplary implementation of FIG. 8, communications agent 800 comprising the described data structure 806. 如下文参考图10将要详细介绍的,数据结构806可以包括存储器空间、IO空间、配置空间和消息空间,所述空间由通信引擎804使用以便于EGIO体系结构的元件之间进行通信。 As described with reference to FIG. 10 will be described in detail, the data structure 806 may include memory space, IO space, configuration space and message space to facilitate communication between the elements of the EGIO architecture of the space used by the communications engine 804.

如这里所使用的,应用808被规定为代表由通信引擎800选择性调用的多种应用的任何一种,以实现EGIO通信协议和相关的管理功能。 As used herein, the application 808 is defined as any of a variety of applications represented by communication engine 800 selectively invoked to achieve EGIO communication protocol and associated management functions. 根据一个示例性实现,带宽管理器、流控制机制、数据完整性机制和对老式中断的支持被实现为通信代理800中的可执行内容,所述可执行内容可由EGIO通信引擎804的一个或多个合适元件有选择地调用。 According to an exemplary implementation, the bandwidth manager, flow control mechanisms, and the old data integrity mechanisms are implemented to support interrupts communication broker executable content 800, the executable content may be an EGIO communication engine 804 or more a suitable element is selectively called.

示例性(多种)数据结构参考图10,描述了(多个)EGIO接口106使用的一种或多种数据结构的示图。 Exemplary (s) with reference to the data structure of FIG. 10, EGIO interface 106 shown in FIG one or more data structures using the described (s). 根据本发明的一个实现,更具体地说,参考图10所图示的示例性实现,定义了四(4)个地址空间以在EGIO体系结构中使用:配置空间1010、IO空间1020、存储器空间1030以及消息空间1040。 According to one implementation of the present invention, more specifically, with reference to FIG. 10, the illustrated exemplary implementation, the definition of four (4) address space used in EGIO architecture: the configuration space 1010, IO space 1020, memory space 1030 and 1040 message space. 如所示,配置空间1010包括头部字段1012,其包括定义了EGIO类别的信息,其中主设备(例如,端点、交换器、根复合体等等)属于该类别。 As shown, configuration space header 1010 includes fields 1012, which defines the EGIO category includes information, wherein the master device (e.g., endpoint, switches, root complex, etc.) belongs to this category. 这些地址空间的每个都执行他们如上所述的各自功能。 Each of these address spaces perform their respective functions as described above.

其它实施例图12是根据本发明另一个实施例的其上存有多个指令的存储器介质的方框图,其中所述指令包括实现EGIO互连体系结构和通信协议的一个或多个方面的指令。 Other embodiments FIG. 12 is a block diagram of which there are a plurality of instructions on a memory medium of embodiment according to another embodiment of the present invention, wherein the instruction comprises achieve EGIO interconnection architecture and a communication protocol or more aspects of the instruction.

大体而言,图12图示了其上(中)存储有内容1202的机器可访问介质/设备1200,所述内容包括以下内容的至少一个子集,即当访问机器执行所述内容时,所述内容实现了本发明的创新EGIO接口106。 In general, Figure 12 illustrates thereon (in) 1202 stores contents of machine accessible medium / device 1200, the content comprising at least a subset of the content, that is, when accessing the machine to perform the content, the said contents implements the innovative EGIO interface 106 of the present invention. 如这里所使用的,机器可访问介质1200被规定为代表本领域技术人员公知的多种介质的任何一个,例如易失性存储器设备、非易失性存储器设备、磁存储介质、光存储介质、传播信号等等。 As used herein, machine accessible medium 1200 is specified as a representative of any well known to those skilled in the various media, such as volatile memory devices, nonvolatile memory devices, magnetic storage media, optical storage media, propagated signal, and so on. 类似地,可执行指令被规定为表达本领域公知的多种软件语言的任何一种,例如C++、Visual Basic、超文本标记语言(HTML)、Java、可扩充标记语言(XML)等等。 Similarly, the executable instructions is defined as any known in the art as an expression of a variety of software languages, such as C ++, Visual Basic, HTML (HTML), Java, Extensible Markup Language (XML), and so on. 此外,应当认识到介质1200不需要与任何主系统共处在一起。 In addition, it should be recognized that the media does not need to coexist together in 1200 with any host system. 即,介质1200可以位于远程服务器中,所述服务器可通信地耦合到执行系统并可由执行系统访问。 That is, the media 1200 may be located in a remote server, the server may be communicatively coupled to the system may be executed by the execution system access. 因此,图12的软件实现应当认为是示例性的,因为另一个存储介质与软件实施例被认为位于本发明的精神和范围之内。 Therefore, the software 12 of FIG realization to be considered exemplary, as other storage media and software embodiments are considered to be within the spirit of the present invention located and scope.

尽管以详细的描述以及对结构特征和/或方法步骤的专用语言的抽象描述了本发明,但是应当理解,在所附权利要求中定义的本发明不必限制为所描述的具体特征或步骤。 Although the detailed description and abstract structural features and / or method steps described in the specific language of the present invention, it should be understood as defined in the appended claims of the present invention is not necessarily limited to the specific features or steps described. 相反,所述具体特征和步骤只是作为实现所主张的发明的示例性形式而被公开。 Instead, the specific features and steps just as the implementation of the claimed invention is disclosed exemplary forms. 然而很明显,可以对其进行各种修改和变化而不会背离本发明较宽的精神和范围。 Clearly, however, it can be a variety of modifications and variations of the present invention without departing from the broader spirit and scope. 因此本说明书和附图被认为是示例性的而不是限制性的。 The specification and drawings are to be regarded as illustrative rather than restrictive. 说明书和摘要没有被规定为是穷尽性的或是要将本发明限制为所公开的确定形式。 Description and summary is not intended to be exhaustive or to limit the invention to determine the form disclosed.

所附权利要求中使用的术语不应被解释成将本发明限制为说明书中公开的具体实施例。 The term used in the appended claims should not be construed as to limit the invention to the specific embodiments disclosed in the specification. 相反,所附权利要求完全确定了本发明的范围,其中根据已有权利要求解释原则来解释所述权利要求。 On the contrary, fully defined the scope of the appended claims the invention, wherein the claim interpreted in accordance with established principles of claim construction.

Classifications
International ClassificationG06F3/00, G06F13/14, G06F13/24, G06F13/12, G06F13/00, H04L1/18
Cooperative ClassificationH04L47/30, G06F13/4221, H04L47/10, G06F5/06, G06F13/124, G06F13/385, G06F13/4282, G06F13/4265, G06F13/4059, G06F13/42, G06F13/4252, G06F13/4269
European ClassificationG06F13/12P
Legal Events
DateCodeEventDescription
17 Nov 2004C06Publication
26 Jan 2005C10Entry into substantive examination
6 Feb 2008C14Grant of patent or utility model