会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 2. 发明授权
    • Method and apparatus for maintaining an order of write operations by
processors in a multiprocessor computer to maintain memory consistency
    • 用于维护多处理器计算机中的处理器的写入操作顺序以维持存储器一致性的方法和装置
    • US5900020A
    • 1999-05-04
    • US678372
    • 1996-06-27
    • Robert J. SafranekThomas D. LovettRobert T. JoerszBruce M. Gilbert
    • Robert J. SafranekThomas D. LovettRobert T. JoerszBruce M. Gilbert
    • G06F12/08G06F13/14G06F13/24G06F13/42
    • G06F12/0828G06F12/0813G06F2212/2542
    • A method and apparatus for maintaining processor consistency in a multiprocessor computer such as a multinode computer system are disclosed. A processor proceeds with write operations before its previous write operations complete, while processor consistency is maintained. A write operation begins with a request by the processor to invalidate copies of the data stored in other nodes. This current invalidate request is queued while acknowledging to the processor that the request is complete even though it has not actually completed. The processor proceeds to complete the write operation by changing the data. It can then execute subsequent operations, including other write operations. The queued request, however, is not transmitted to other nodes in the computer until all previous invalidate requests by the processor are complete. This ensures that the current invalidate request will not pass a previous invalidate request. The invalidate requests are added and removed from a processor's outstanding invalidate list as they arise and are completed. An invalidate request is completed by notifying the nodes in a linked list related to the current invalidate request that data shared by the node is now invalid.
    • 公开了一种在诸如多节点计算机系统的多处理器计算机中维持处理器一致性的方法和装置。 处理器在其先前的写入操作完成之前进行写入操作,同时保持处理器的一致性。 写入操作从处理器的请求开始,使存储在其他节点中的数据的副本无效。 该当前无效请求被排队,同时向处理器确认请求完成,即使它尚未实际完成。 处理器继续通过更改数据来完成写入操作。 然后,它可以执行后续操作,包括其他写入操作。 然而,排队的请求不会传输到计算机中的其他节点,直到处理器的所有先前的无效请求都完成为止。 这确保当前的无效请求不会通过先前的无效请求。 无效请求在处理器未完成的无效列表出现并被完成时被添加和删除。 通过通知与当前无效请求相关的链接列表中的节点,节点共享的数据现在无效,则完成无效请求。
    • 3. 发明授权
    • Maintaining order of write operations in a multiprocessor for memory consistency
    • 维护多处理器中写入操作的顺序,以保持内存一致性
    • US06493809B1
    • 2002-12-10
    • US09493782
    • 2000-01-28
    • Robert J. SafranekThomas D. Lovett
    • Robert J. SafranekThomas D. Lovett
    • G06F1300
    • G06F13/4243
    • A method of invalidating shared cache lines such as on a sharing list by issuing an invalidate acknowledgement before actually invalidating a cache line. The method is useful in multiprocessor systems such as a distributed shared memory (DSM) or non-uniform memory access (NUMA) machines that include a number of interconnected processor nodes each having local memory and caches that store copies of the same data. In such a multiprocessor system using the Scalable Content Interface (SCI) protocol, an invalidate request is sent from the head node on the sharing list to a succeeding node on the list. In response to the invalidate request, the succeeding node issues an invalidate acknowledgement before the cache line is actually invalidated. After issuing the invalidate acknowledgement, the succeeding node initiates invalidation of the cache line. The invalidate acknowledgement can take the form of a response to the head node or a forwarding of the invalidate request to the next succeeding node on the list. To maintain processor consistency, a flag is set each time an invalidate acknowledgement is sent. The flag is cleared after the invalidation of the cache line is completed. Cacheable transactions received at the succeeding node while a flag is set are delayed until the flag is cleared.
    • 一种使共享高速缓存行无效化的方法,例如在共享列表上通过在实际使高速缓存行无效之前发出无效确认。 该方法在诸如分布式共享存储器(DSM)或非均匀存储器访问(NUMA)机器的多处理器系统中是有用的,其包括多个互连的处理器节点,每个互连处理器节点具有存储相同数据的副本的本地存储器和高速缓存。 在使用可伸缩内容接口(SCI)协议的这种多处理器系统中,将无效请求从共享列表上的头节点发送到列表上的后续节点。 响应于无效请求,后续节点在高速缓存行实际无效之前发出无效确认。 发出无效确认后,后续节点启动高速缓存行的无效。 无效确认可以采取对头节点的响应的形式或将无效请求转发到列表上的下一个后续节点。 为了保持处理器的一致性,每次发送无效确认时都会设置一个标志。 标志在高速缓存行无效完成后被清除。 在设置标志时在后续节点处接收的可缓存事务被延迟直到该标志被清除。