Patent Application
20060010281
The present invention relates generally to interconnection architecture, and particularly to interconnecting multiple processors with multiple shared memories.
Advances in the area of computer graphics algorithms have led to the ability to create realistic and complex images, scenes and films using sophisticated techniques such as ray tracing and rendering. However, many complex calculations must be executed when creating realistic or complex images. Some images may take days to compute even when using a computer with a fast processor and large memory banks. Multiple processor systems have been developed in an effort to speed up the generation of complex and realistic images. Because graphics calculations tend to be memory intensive applications, some multiple processor graphics systems are outfitted with multiple, shared memory banks. Ideally, a multiple processor, multiple memory bank system would have full, fast interconnection between the memory banks and processors. For systems with a limited number of processors and memory banks, a crossbar switch is an excellent choice for providing fast, full interconnection without introducing bottlenecks.
However, conventional crossbar-based architectures do not scale well for a graphics system with a large number of processors. Typically, the size of a crossbar switch is limited by processing and/or packaging technology constraints such as the maximum number of pins per chip. In particular, such technology constraints restrict the size of a data word that can be switched by conventional crossbar switches.
In general, in one aspect, the invention features a method and apparatus. It includes identifying a first portion of a first message in a first slice of a switch, the first message associated with a first priority, the first portion of the first message including a first routing portion specifying a network resource; identifying a second portion of the first message in a second slice of the switch, the second portion of the first message including the first routing portion; identifying a first portion of a second message in the first slice, the second message associated with a second priority, the first portion of the second message including a second routing portion specifying the network resource; identifying a second portion of the second message in the second slice, the second portion of the second message including the second routing portion; selecting, independently in each slice, the same one of the first and second messages based on the first and second priorities; sending the first portion of the selected message from the first slice to the network resource specified by the one of the first and second routing portions corresponding to the selected message; and sending the second portion of the selected message from the second slice to the network resource specified by the one of the first and second routing portions corresponding to the selected message.
Particular implementations can include one or more of the following features Implementations include associating the first and second priorities with the first and second messages based on the ages of the first and second messages. Implementations include dividing each message to create the first and second portions; sending the first portions to the first slice; and sending the second portions to the second slice. The network resource is a memory resource. The network resource is a processor. The network resource is a crossbar.
In general, in another aspect, the invention features a method and apparatus for use in a first slice of a switch having first and second slices. It includes identifying a first portion of a first message, the first message associated with a first priority, the first portion of the first message including a first routing portion specifying a network resource, wherein a second portion of the first message resides in the second slice, the second portion of the first message including the first routing portion; identifying a first portion of a second message in the first slice, the second message associated with a second priority, the first portion of the second message including a second routing portion specifying the network resource, wherein a second portion of the second message resides in the second slice, the second portion of the second message including the second routing portion; selecting one of the first and second messages based on the first and second priorities, wherein the second slice independently selects the same one of the first and second messages based on the first and second priorities; and sending the first portion of the selected message from the first slice to the network resource specified by the one of the first and second routing portions corresponding to the selected message; and wherein the second slice sends the second portion of the selected message from the second slice to the network resource specified by the one of the first and second routing portions corresponding to the selected message.
Particular implementations can include one or more of the following features. The network resource is a memory resource. The network resource is a processor. The network resource is a crossbar.
Advantages that can be seen in implementations of the invention include one or more of the following. The architectures disclosed herein permit very large data words to be switched by a number of crossbar switch slices operating in parallel. In addition, no inter-slice communication is required.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.
Like reference symbols in the various drawings indicate like elements.
Introduction
As shown in
Each processor group PG includes a plurality of processor switches PSW0 through PSW7. Each processor switch PSW includes a plurality of processors P0 through P3. Each processor P is connected to a processor crossbar PXB. In one implementation, each of processors P0 through P3 performs a different graphics rendering function. In one implementation, P0 is a triangle processor, P1 is a triangle intersector, P2 is a ray processor, and P3 is a grid processor.
Each switch group SG includes a plurality of switch crossbars SXB0 through SXB7. Each processor crossbar PXB is connected to one switch crossbar SXB in each switch group SG. Each switch crossbar SXB in a switch group SG is connected to a different processor crossbar PXB in a processor group PG. For example, the processor crossbar PXB in processor switch PSW0 is connected to switch crossbar SXB0 in switch group SG0, while the processor crossbar in processor switch PSW7 is connected to switch crossbar SXB7 in switch group SG0.
Each memory switch MSW includes a plurality of memory controllers MC0 through MC7. Each memory controller MC is connected to a memory crossbar MXB by an internal bus. Each memory controller MC is also connected to one of a plurality of memory tracks T0 through T7. Each memory track T includes a plurality of memory banks. Each memory track T can be implemented as a conventional memory device such as a SDRAM.
Each memory group MG is connected to one switch group SG. In particular, each memory crossbar MXB in a memory group MG is connected to every switch crossbar SXB in the corresponding switch group SG.
Processor crossbars PXB provide full crossbar interconnection between processors P and switch crossbars SXB. Memory crossbars MXB provide full crossbar interconnection between memory controllers MC and switch crossbars SXB. Switch crossbars SXB provide full crossbar interconnection between processor crossbars PXB and memory crossbars MXB.
In one implementation, each of processor switches PSW, memory switches MSW and switch crossbars SXB is fabricated as a separate semiconductor chip. In one implementation, each processor switch PSW is fabricated as a single semiconductor chip, each switch crossbar SXB is fabricated as two or more semiconductor chips that operate in parallel, each memory crossbar MXB is fabricated as two or more semiconductor chips that operate in parallel, and each memory track T is fabricated as a single semiconductor chip. One advantage of each of these implementations is that the number of off-chip interconnects is minimized. Such implementations are disclosed herein and in a copending patent application entitled “SLICED CROSSBAR ARCHITECTURE WITH INTER-SLICE COMMUNICATION,” Ser. No. 09/927,306, filed Aug. 9, 2001.
Slice Architecture
In other implementations, each of crossbars SXB and MXB includes more than two slices. In one implementation, crossbars SXB and MXB also send messages from memory track T to processor P using the techniques described below. After reading this description, these implementations and techniques will be apparent to one skilled in the relevant arts.
Processor P sends a message RSMBX to processor crossbar PXB. Processor crossbar PXB sends messages to switch crossbar SXB by sending a portion of the message to each of slices SXBA and SXBB. One implementation includes multiple switch crossbars SXB. Message RSMBX includes a routing portion R that is the address of switch crossbar SXB. In one implementation, processor crossbar PXB discards any routing information that is no longer needed. For example, routing information R is the address of switch crossbar SXB, and is used to route message SMBX to switch crossbar SXB. Then routing information R is no longer needed and so is discarded.
Referring to
Each switch crossbar SXB stores each received message portion in a buffer BUFSXB. For example, switch crossbar SXBA stores message portion SMBX1 in buffer BUFSXBA and switch crossbar SXBB stores message portion SMBX2 in buffer BUFSXBB. Each message in buffer BUFSXBA is assigned a priority with respect to the other message portions in buffer BUFSXBA. Each message in buffer BUFSXBB is assigned a priority with respect to the other message portions in buffer BUFSXBB. In one implementation, each message is assigned a priority based on time of arrival at the buffer. In one implementation, each of buffers BUFSX
Arbiter ARBSXBA identifies message portion SMBX1 and the priority associated with message portion SMBX1 (step 302). Arbiter ARBSXBB identifies message portion SMBX2 and the priority associated with message portion SMBX2 (step 304).
One implementation includes multiple memory crossbars MXB. The address portions SMB of message portions SMBX1 and SMBX2 include a routing portion S identifying memory crossbar MXB.
Arbiter ARBSXBA identifies message portion SMBY1 and the priority associated with message portion SMBY1 (step 306). Arbiter ARBSXBB identifies message portion SMBY2 and the priority associated with message portion SMBY2 (step 308). The address portions SMB of message portions SMBY1 and SMBY2 also include a routing portion S identifying memory crossbar MXB.
Both messages SMBX and SMBY specify the same memory resource (memory crossbar MXB). Accordingly, arbiter ARBSXBA selects the message having the higher priority. Arbiter ARBSXBB employs the same priority scheme as arbiter ARBSXBA, and so independently selects the same message. Assume that message SMBX has a higher priority than message SMBY. Accordingly, each of arbiters ARBSXBA and ARBSXBB independently selects message SMBX (step 310).
In one implementation, switch crossbar SXB discards any routing information that is no longer needed. For example, routing information S is the address of memory crossbar MXB, and is used to route message portions MBX1 and MBX2 to memory crossbar MXB. Then routing information S is no longer needed and so is discarded.
Arbiter ARBSXBA causes multiplexer MUXSXBA to gate message portion SMBX1 to memory crossbar MXB (step 312). Arbiter ARBSXBB causes multiplexer MUXSXBB to gate message portion SMBX2 to memory crossbar MXB (step 314).
Each memory crossbar MXB stores each received message portion in a buffer BUFMXB. For example, memory crossbar MXBA stores message portion MBX1 in buffer BUFMXBA and memory crossbar MXBB stores message portion MBX2 in buffer BUFMXBB. Each message portion in buffer BUFMXBA is assigned a priority with respect to the other message portions in buffer BUFMXBA. Each message in buffer BUFMXBB is assigned a priority with respect to the other message portions in buffer BUFMXBB. In one implementation, each message is assigned a priority based on time of arrival at the buffer. In one implementation, each of buffers BUFMXBA and BUFMXBB is implemented as a queue, and the priority of each message is determined by its position in the queue.
Arbiter ARBMXBA identifies message portion MBX1 and the priority associated with message portion MBX1 (step 402). Arbiter ARBMXBB identifies message portion MBX2 and the priority associated with message portion MBX2 (step 404).
One implementation includes multiple memory tracks T. The routing portions M of the address portions MB of message portions MBX1 and MBX2 identify memory track T. Arbiter ARBMXBA identifies message portion MBY1 and the priority associated with message portion MBY1 (step 406). Arbiter ARBMXBB identifies message portion MBY2 and the priority associated with message portion MBY2 (step 408). The address portions MB of message portions MBY1 and MBY2 also include a routing portion M identifying memory crossbar MXB.
Both messages MBX and MBY specify the same memory resource (memory track T). Accordingly, arbiter ARBMXBA selects the message having the higher priority. Arbiter ARBMXBB employs the same priority scheme as arbiter ARBMXBA, and so independently selects the same message. Assume that message MBX has a higher priority than message MBY. Accordingly, each of arbiters ARBMXBA and ARBMXBB independently selects message MBX (step 410).
In one implementation, memory crossbar MXB discards any routing portion that is no longer needed. For example, routing portion M is the address of memory track T, and is used to route message portions BX1 and BX2 to memory track T. Then routing information M is no longer needed and so is discarded.
Arbiter ARBMXBA causes multiplexer MUXMXBA to gate message portion BX1 to memory track T (step 412). Arbiter ARBMXBB causes multiplexer MUXMXBB to gate message portion BX2 to memory track T (step 414). In one implementation, both routing portions B specify the same memory bank within memory track T.
Architecture Overview
Referring to
Each processor 502 is coupled by a pair of busses 516 and 517 to one of the processor crossbars 508. For example, processor 502A is coupled by busses 516A and 517A to processor crossbar 508A. In a similar manner, processor 502N is coupled by busses 516N and 517N to processor crossbar 508N. In one implementation, each of busses 516 and 517 includes many point-to-point connections.
Each processor crossbar 508 includes a plurality of input ports 538A through 538M, each coupled to a bus 516 or 517 by a client interface 518. For example, client interface 518 couples input port 538A in processor crossbar 508A to bus 516A, and couples input port 538M in processor crossbar 508A to bus 517A. In one implementation, M=8. In other implementations, M takes on other values, and can take one different values for each type of port, and can differ from crossbar to crossbar.
Each processor crossbar 508 also includes a plurality of output ports 540A through 540M. Each of the input ports 538 and output ports 540 are coupled to an internal bus 536. In one implementation, each bus 536 includes many point-to-point connections. Each output port 540 is coupled by a segment interface 520 to one of a plurality of busses 522A through 522M. For example, output port 540A is coupled by segment interface 520 to bus 522A. Each bus 522 couples processor crossbar 508A to a different switch crossbar 510. For example, bus 522A couples processor crossbar 508A to switch crossbar 510A. In one implementation, busses 522 include many point-to-point connections.
Each switch crossbar 510 includes a plurality of input ports 544A through 544M, each coupled to a bus 522 by a segment interface 524. For example, input port 544A in switch crossbar 510A is coupled to bus 522A by segment interface 524.
Each switch crossbar 510 also includes a plurality of output ports 546A through 546M. Each of the input ports 544 and output ports 546 are coupled to an internal bus 542. In one implementation, each bus 542 includes many point-to-point connections. Each output port 546 is coupled by a segment interface 526 to one of a plurality of busses 528A through 528M. For example, output port 546A is coupled by segment interface 526 to bus 528A. Each bus 528 couples switch crossbar 510A to a different memory crossbar 512. For example, bus 528A couples switch crossbar 510A to memory crossbar 512A. In one implementation, each of busses 528 includes many point-to-point connections.
Each memory crossbar 512 includes a plurality of input ports 550A through 550M, each coupled to a bus 528 by a segment interface 530. For example, input port 550A in memory crossbar 512A is coupled to bus 528A by segment interface 530.
Each memory crossbar 512 also includes a plurality of output ports 552A through 552M. Each of the input ports 550 and output ports 552 are coupled to an internal bus 548. In one implementation, each bus 548 includes many point-to-point connections. Each output port 552 is coupled by a memory controller 532 to one of a plurality of busses 534A through 534M. For example, output port 552A is coupled by memory controller 532 to bus 534A. Each of busses 534A through 534M couples memory crossbar 512A to a different one of memory tracks 504A through 504M. Each memory track 504 includes one or more synchronous dynamic random access memories (SDRAMs), as discussed below. In one implementation, each of busses 534 includes many point-to-point connections.
In one implementation, each of busses 516, 517, 522, 528, and 534 is a high-speed serial bus where each transaction can include one or more clock cycles. In another implementation, each of busses 516, 517, 522, 528, and 534 is a parallel bus. Conventional flow control techniques can be implemented across each of busses 516, 522, 528, and 534. For example, each of client interface 518, memory controller 532, and segment interfaces 520, 524, 526, and 530 can include buffers and flow control signaling according to conventional techniques.
In one implementation, each crossbar 508, 510, 512 is implemented as a separate semiconductor chip. In one implementation, processor crossbar 508 and processor 502 are implemented together as a single semiconductor chip. In one implementation, each of switch crossbar 510 and memory crossbar 512 is implemented as two or more chips that operate in parallel, as described below.
Processor
Referring to
Clients 602 manage memory requests from processes executing within processor 502. Clients 602 collect memory transactions (MT) destined for memory. If a memory transaction cannot be satisfied by a cache 606, the memory transaction is sent to memory. Results of memory transactions (Result) may return to client funnel 604 out of order. Reorder unit 608 arranges the results in order before passing them to a client 602.
Each input port 538 within processor crossbar 508 asserts a POPC signal when that input port 538 can accept a memory transaction. In response, client funnel 604 sends a memory transaction to that input port 538 if client funnel 604 has any memory transactions destined for that input port 538.
Processor Crossbar
Referring to
Queue 704 includes a queue controller 710 and four request stations 712A, 712B, 712C, and 712D. In one implementation, request stations 712 are implemented as registers. In another implementation, request stations 712 are signal nodes separated by delay elements. Queue controller 710 can be implemented using conventional Boolean logic devices.
Now an example operation of input port 538 in passing a memory transaction from processor 502 to switch crossbar 510 will be described with reference to
Internal bus 536 includes 64 data busses including 32 forward data busses and 32 reverse data busses. Each request station 712 in each input port 538 is coupled to a different one of the 32 forward data busses. In this way, the contents of all of the request stations 712 are presented on internal bus 536 simultaneously.
Each memory transaction includes a command and a memory address. Some memory transactions, such as write transactions, also include data. For each memory transaction, queue controller 710 asserts a request REQC for one of output ports 540 based on a portion of the address in that memory transaction. Queue controller 710 also asserts a valid signal VC for each request station 712 that currently stores a memory transaction ready for transmission to switch crossbar 510.
Each output port 540 chooses zero or one of the request stations 712 and transmits the memory transaction in that request station to switch crossbar 510, as described below. That output port 540 asserts a signal ACKC that tells the input port 538 which request station 712 was chosen. If one of the request stations 712 within input port 538 was chosen, queue controller 710 receives an ACKC signal. The ACKC signal indicates one of the request stations 712.
The request stations 712 within a queue 704 operate together substantially as a buffer. New memory transactions from processor 502 enter at request station 712A and progress towards request station 712D as they age until chosen by an output port. For example, if an output port 540 chooses request station 712B, then request station 712B becomes invalid and therefore available for a memory transaction from processor 502. However, rather than placing a new memory transaction in request station 712B, queue controller 710 moves the contents of request station 712A into request station 712B and places the new memory transaction in request station 712A. In this way, the identity of a request station serves as an approximate indicator of the age of the memory transaction. In one implementation, only one new memory transaction can arrive during each transaction time, and each memory transaction can age by only one request station during each transaction time. Each transaction time can include one or more clock cycles. In other implementations, age is computed in other ways.
When queue controller 710 receives an ACKC signal, it takes three actions. Queue controller 710 moves the contents of the “younger” request stations 712 forward, as described above, changes the status of any empty request stations 712 to invalid by disasserting VC, and sends a POPC signal to client interface 518. Client interface segment 518 forwards the POPC signal across bus 516 to client funnel 604, thereby indicating that input port 538 can accept a new memory transaction from client funnel 604.
In response, client funnel 604 sends a new memory transaction to the client interface 518 of that input port 538. Client funnel 604 also sends a tag TAGC that identifies the client 602 within processor 502 that generated the memory transaction.
Queue controller 710 stores the new memory transaction and the TAGC in request station 712A, and asserts signals VC and REQC for request station 712A. Signal VC indicates that request station 712A now has a memory transaction ready for transmission to switch crossbar 510. Signal REQC indicates through which output port 540 the memory transaction should pass.
Referring to
Queue 804 includes a queue controller 810 and four request stations 812A, 812B, 812C, and 812D. In one implementation, request stations 812 are implemented as registers. In another implementation, request stations 812 are signal nodes separated by delay elements. Queue controller 810 can be implemented using conventional Boolean logic devices.
Now an example operation of output port 540 in passing a memory transaction from an input port 538 to switch crossbar 510 will be described with reference to
Arbiter 806 causes multiplexer 808 to gate the memory transaction (MT) within the chosen request station 712 to segment interface 520. Arbiter 806 generates a signal IDP that identifies the input port 538 within which the chosen request station 712 resides. The identity of that input port 538 is derived from the REQC signal.
Tag generator 802 generates a tag TAGP according to the methods described below. Arbiter 806 receives the TAGC associated with the memory transaction. The IDP, TAGC, and TAGP are stored in tag buffer 803. In one implementation, any address information within the memory transaction that is no longer needed (that is, the address information that routed the memory transaction to output port 540) is discarded. In another implementation that address information is passed with the memory transaction to switch crossbar 510. Arbiter 806 asserts an ACKC signal that tells the input port 538 containing the chosen request station 712 that the memory transaction in that request station has been transmitted to switch crossbar 510.
Now an example operation of output port 540 in passing a result of a memory transaction from switch crossbar 510 to processor 502 will be described with reference to
As mentioned above, internal bus 536 includes 32 reverse data busses. Each request station 812 in each output port 540 is coupled to a different one of the 32 reverse data busses. In this way, the contents of all of the request stations 812 are presented on internal bus 536 simultaneously.
Some results, such as a result of a read transaction, include data. Other results, such as a result for a write transaction, include an acknowledgement but no data. For each result, queue controller 810 asserts a request REQP for one of input ports 538 based on IDP. As mentioned above, IDP indicates the input port 538 from which the memory transaction prompting the result originated. Queue controller 810 also asserts a valid signal VP for each request station 812 that currently stores a result ready for transmission to processor 502.
Each input port 538 chooses zero or one of the request stations 812 and transmits the result in that request station to processor 502, as described below. That input port 538 asserts a signal ACKP that tells the output port 540 which request station 812 within that output port was chosen. If one of the request stations 812 within output port 540 was chosen, queue controller 810 receives an ACKP signal. The ACKP signal indicates one of the request stations 812.
The request stations 812 within a queue 804 operate together substantially as a buffer. New results from processor 502 enter at request station 812A and progress towards request station 812D until chosen by an input port 538. For example, if an input port 538 chooses request station 812B, then request station 812B becomes invalid and therefore available for a new result from switch crossbar 510. However, rather than placing a new result in request station 812B, queue controller 810 moves the contents of request station 812A into request station 812B and places the new result in request station 812A. In this way, the identity of a request station 812 serves as an approximate indicator of the age of the result. In one implementation, only one new memory transaction can arrive during each transaction time, and each memory transaction can age by only one request station during each transaction time. In other implementations, age is computed in other ways.
When queue controller 810 receives an ACKP signal, it takes three actions. Queue controller 810 moves the contents of the “younger” request stations forward, as described above, changes the status of any empty request stations to invalid by disasserting VP, and sends a POPB signal to segment interface 520. segment interface 520 forwards the POPB signal across bus 522 to switch crossbar 510, thereby indicating that output port 540 can accept a new result from switch crossbar 510.
In response, switch crossbar 510 sends a new result, and a TAGP associated with that result, to the segment interface 520 of that output port 540. The generation of TAGP, and association of that TAGP with the result, are discussed below with reference to
Tag buffer 803 uses the received TAGP to retrieve the IDP and TAGC associated with that TAGP. TAGP is also returned to TAGP generator 802 for use in subsequent transmissions across bus 522.
Queue controller 810 stores the new result, the TAGP, and the IDP in request station 812A, and asserts signals VP and REQP for request station 812A. Signal VP indicates that request station 812A now has a result ready for transmission to processor 502. Signal REQP indicates through which input port 538 the result should pass.
Now an example operation of input port 538 in passing a result from an output port 540 to processor 502 will be described with reference to
Arbiter 706 causes multiplexer 708 to gate the result and associated TAGC to client interface 518. Arbiter 706 also asserts an ACKP signal that tells the output port 540 containing the chosen request station 812 that the result in that request station has been transmitted to processor 502.
Switch Crossbar
Referring to
Queue 904 includes a queue controller 910 and four request stations 912A, 912B, 912C, and 912D. In one implementation, request stations 912 are implemented as registers. In another implementation, request stations 912 are signal nodes separated by delay elements. Queue controller 910 can be implemented using conventional Boolean logic devices.
Now an example operation of input port 544 in passing a memory transaction from processor crossbar 508 to memory crossbar 512 will be described with reference to
Internal bus 542 includes 64 data busses including 32 forward data busses and 32 reverse data busses. Each request station 912 in each input port 544 is coupled to a different one of the 52 forward data busses. In this way, the contents of all of the request stations 912 are presented on internal bus 542 simultaneously.
Each memory transaction includes a command and a memory address. Some memory transactions, such as write transactions, also include data. For each memory transaction, queue controller 910 asserts a request REQS for one of output ports 546 based on a portion of the address in that memory transaction. Queue controller 910 also asserts a valid signal VS for each request station 912 that currently stores a memory transaction ready for transmission to memory crossbar 512.
Each output port 546 chooses zero or one of the request stations 912 and transmits the memory transaction in that request station to memory crossbar 512, as described below. That output port 546 asserts a signal ACKS that tells the input port 544 which request station 912 was chosen. If one of the request stations 912 within input port 544 was chosen, queue controller 910 receives an ACKS signal. The ACKS signal indicates one of the request stations 912.
The request stations 912 within a queue 904 operate together substantially as a buffer. New memory transactions from processor crossbar 508 enter at request station 912A and progress towards request station 912D as they age until chosen by an output port. For example, if an output port 546 chooses request station 912B, then request station 912B becomes invalid and therefore available for a memory transaction from processor crossbar 508. However, rather than placing a new memory transaction in request station 912B, queue controller 910 moves the contents of request station 912A into request station 912B and places the new memory transaction in request station 912A. In this way, the identity of a request station serves as an approximate indicator of the age of the memory transaction. In one implementation, only one new memory transaction can arrive during each transaction time, and each memory transaction can age by only one request station during each transaction time. In other implementations, age is computed in other ways.
When queue controller 910 receives an ACKS signal, it takes three actions. Queue controller 910 moves the contents of the “younger” request stations 912 forward, as described above, changes the status of any empty request stations 912 to invalid by disasserting VS, and sends a POPP signal to segment interface 524. Segment interface 524 forwards the POPP signal across bus 522 to processor crossbar 508, thereby indicating that input port 544 can accept a new memory transaction from processor crossbar 508.
In response, processor crossbar 508 sends a new memory transaction to the segment interface 524 of that input port 544. TAGP generator 902 generates a TAGP for the memory transaction. Tag generators 902 and 802 are configured to independently generate the same tags in the same order, and are initialized to generate the same tags at substantially the same time, as discussed below. Therefore, the TAGP generated by TAGP generator 902 for a memory transaction has the same value as the TAGP generated for that memory transaction by TAGP generator 802. Thus the tagging technique of this implementation allows a result returned from memory tracks 504 to be matched at processor 502 with the memory transaction that produced that result.
Queue controller 910 stores the new memory transaction and the TAGP in request station 912A, and asserts signals VS and REQS for request station 912A. Signal VS indicates that request station 912A now has a memory transaction ready for transmission to memory crossbar 512. Signal REQS indicates through which output port 546 the memory transaction should pass.
Referring to
Queue 1004 includes a queue controller 1010 and four request stations 1012A, 1012B, 1012C, and 1012D. In one implementation, request stations 1012 are implemented as registers. In another implementation, request stations 1012 are signal nodes separated by delay elements. Queue controller 1010 can be implemented using conventional Boolean logic devices.
Now an example operation of output port 546 in passing a memory transaction from an input port 544 to memory crossbar 512 will be described with reference to
Arbiter 1006 causes multiplexer 1008 to gate the memory transaction (MT) within the chosen request station 912 to segment interface 526. Arbiter 1006 generates a signal IDS that identifies the input port 544 within which the chosen request station 912 resides. The identity of that input port 544 is derived from the REQC signal.
TAGS generator 1002 generates a tag TAGS according to the methods described below. Arbiter 1006 receives the TAGP associated with the memory transaction. The IDS, TAGP, and TAGS are stored in tag buffer 1003. In one implementation, any address information within the memory transaction that is no longer needed (that is, the address information that routed the memory transaction to output port 546) is discarded. In another implementation that address information is passed with the memory transaction to memory crossbar 512. Arbiter 1006 asserts an ACKS signal that tells the input port 544 containing the chosen request station 912 that the memory transaction in that request station has been transmitted to memory crossbar 512.
Now an example operation of output port 546 in passing a result of a memory transaction from memory crossbar 512 to processor crossbar 508 will be described with reference to
As mentioned above, internal bus 542 includes 32 reverse data busses. Each request station 1012 in each output port 546 is coupled to a different one of the 32 reverse data busses. In this way, the contents of all of the request stations 1012 are presented on internal bus 542 simultaneously.
Some results, such as a result of a read transaction, include data. Other results, such as a result for a write transaction, include an acknowledgement but no data. For each result, queue controller 1010 asserts a request REQX for one of input ports 544 based on IDS. As mentioned above, IDS indicates the input port 544 from which the memory transaction prompting the result originated. Queue controller 1010 also asserts a valid signal VX for each request station 1012 that currently stores a result ready for transmission to processor crossbar 508.
Each input port 544 chooses zero or one of the request stations 1012 and transmits the result in that request station to processor crossbar 508, as described below. That input port 544 asserts a signal ACKX that tells the output port 546 which request station 1012 within that output port was chosen. If one of the request stations 1012 within output port 546 was chosen, queue controller 1010 receives an ACKX signal. The ACKX signal indicates one of the request stations 1012.
The request stations 1012 within a queue 1004 operate together substantially as a buffer. New results from processor crossbar 508 enter at request station 1012A and progress towards request station 1012D until chosen by an input port 544. For example, if an input port 544 chooses request station 1012B, then request station 1012B becomes invalid and therefore available for a new result from memory crossbar 512. However, rather than placing a new result in request station 1012B, queue controller 1010 moves the contents of request station 1012A into request station 1012B and places the new result in request station 1012A. In this way, the identity of a request station 1012 serves as an approximate indicator of the age of the result. In one implementation, only one new memory transaction can arrive during each transaction time, and each memory transaction can age by only one request station during each transaction time. In other implementations, age is computed in other ways.
When queue controller 1010 receives an ACKX signal, it takes three actions. Queue controller 1010 moves the contents of the “younger” request stations forward, as described above, changes the status of any empty request stations to invalid, and sends a POPA signal to segment interface 526. Segment interface 526 forwards the POPA signal across bus 522 to memory crossbar 512, thereby indicating that output port 546 can accept a new result from memory crossbar 512.
In response, memory crossbar 512 sends a new result, and a TAGS associated with that result, to the segment interface 526 of that output port 546. The generation of TAGS, and association of that TAGS with the result, are discussed below with reference to
Tag buffer 1003 uses the received TAGS to retrieve the IDS and TAGP associated with that TAGS. TAGS is also returned to TAGS generator 1002 for use in subsequent transmissions across bus 528.
Queue controller 1010 stores the new result, the TAGP, and the IDS in request station 1012A, and asserts signals VX and REQX for request station 1012A. Signal VX indicates that request station 1012A now has a result ready for transmission to processor crossbar 508. Signal REQX indicates through which input port 544 the result should pass.
Now an example operation of input port 544 in passing a result from an output port 546 to processor crossbar 508 will be described with reference to
Arbiter 906 causes multiplexer 908 to gate the result and associated TAGP to segment interface 524, and to return the TAGP to TAGP generator 902 for use with future transmissions across bus 522. Arbiter 906 also asserts an ACKX signal that tells the output port 546 containing the chosen request station 1012 that the result in that request station has been transmitted to processor crossbar 508.
Memory Crossbar
Referring to
Now an example operation of input port 550 in passing a memory transaction from switch crossbar 510 to a memory track 504 will be described with reference to
The request stations 1112 within a queue 1104 operate together substantially as a buffer. New memory transactions from switch crossbar 510 enter at request station 1112A and progress towards request station 1112F until chosen by an output port 552. For example, if an output port 552 chooses request station 1112B, then request station 1112B becomes invalid and therefore available for a memory transaction from switch crossbar 510. However, rather than placing a new memory transaction in request station 1112B, queue controller 1110 moves the contents of request station 112A into request station 112B and places the new memory transaction in request station 112A. In this way, the identity of a request station serves as an approximate indicator of the age of the memory transaction. In one implementation, only one new memory transaction can arrive during each transaction time, and each memory transaction can age by only one request station during each transaction time. In other implementations, age is computed in other ways.
For each memory transaction, queue controller 1110 asserts a request REQM for one of output ports 552 based on a portion of the address in that memory transaction. Queue controller 1110 also asserts a valid signal V for each request station that currently stores a memory transaction ready for transmission to memory tracks 504.
Internal bus 542 includes 64 separate two-way private busses. Each private bus couples one input port 550 to one output port 552 so that each input port has a private bus with each output port.
Each arbiter 1106 includes eight pre-arbiters (one for each private bus). Each multiplexer 1120 includes eight pre-multiplexers (one for each private bus). Each pre-arbiter causes a pre-multiplexer to gate zero or one of the request stations 1112 to the private bus connected to that pre-multiplexer. In this way, an input port 550 can present up to six memory transactions on internal bus 548 simultaneously.
A pre-arbiter selects one of the request stations based on several criteria. The memory transaction must be valid. This information is given by the V signal. The memory transaction in the request station must be destined to the output port 552 served by the pre-arbiter. This information is given by the REQM signal. The memory bank addressed by the memory transaction must be ready to accept a memory transaction. The status of each memory bank is given by a BNKRDY signal generated by output ports 552, as described below. The pre-arbiter considers the age of each memory transaction as well. This information is given by the identity of the request station 1112.
Each output port 552 sees eight private data busses, each presenting zero or one memory transactions from an input port 550. Each output port 552 chooses zero or one of the memory transactions and transmits that memory transaction to memory controller 532, as described below. That output port 552 asserts a signal ACKM that tells the input port 550 which bus, and therefore which input port 550, was chosen. If one of the request stations 1112 within input port 550 was chosen, the pre-arbiter for that bus receives an ACKM signal. The ACKM signal tells the pre-arbiter that the memory transaction presented on the bus served by that pre-arbiter was transmitted to memory. The pre-arbiter remembers which request station 1112 stored that memory transaction, and sends a signal X to queue controller 1110 identifying that request station 1112.
Queue controller 1110 takes several actions when it receives a signal X. Queue controller 1110 moves the contents of the “younger” request stations forward, as described above, changes the status of any empty request stations to invalid by disasserting V, and moves the TAGS for the memory transaction just sent into a delay unit 1108.
Queue controller 1110 also sends a POPM signal to segment interface 530. Segment interface 530 forwards the POPM signal across bus 528 to switch crossbar 510, thereby indicating that input port 550 can accept a new memory transaction from switch crossbar 510.
In response, switch crossbar 510 sends a new memory transaction to the segment interface 530 of that input port 550. TAGS generator 1102 generates a TAGS for the memory transaction. TAGS generators 1102 and 1002 are configured to independently generate the same tags in the same order, and are initialized to generate the same tags at substantially the same time, as discussed below. Therefore, the TAGS generated by TAGS generator 1102 for a memory transaction has the same value as the TAGS generated for that memory transaction by TAGS generator 1002. Thus the tagging technique of this implementation allows a result returned from memory tracks 504 to be returned to the process that originated the memory transaction that produced that result.
Queue controller 1110 stores the new memory transaction and the TAGS in request station 1112A, and asserts signals V and REQM. Signal Vindicates that request station 112A now has a memory transaction ready for transmission to memory tracks 504. Signal REQM indicates through which input port 544 the result should pass.
Referring to
Now an example operation of output port 552 in passing a memory transaction from an input port 550 to a memory track 504 will be described with reference to
Arbiter 1206 causes multiplexer 1208 to gate the memory transaction presented by the chosen input port 550 to memory controller 532. Arbiter 1206 also gates the command and address within the request station to memory controller 532. Arbiter 1206 asserts an ACKM signal that tells the input port 550 containing the chosen request station 1112 that the memory transaction in that request station has been transmitted to memory tracks 504.
Now an example operation of output port 552 in passing a result of a memory transaction from memory tracks 504 to switch crossbar 510 will be described with reference to
Now an example operation of input port 550 in passing a result from an output port 552 to switch crossbar 510 will be described with reference to
Queue 1104 operates according to transaction cycles. A transaction cycle includes a predetermined number of clock cycles. Each transaction cycle queue 1104 may receive a new memory transaction (MT) from a switch crossbar 510. As described above, new memory transactions (MT) are received in request station 1112A, and age through queue 1104 each transaction cycle until selected by a signal X. Request station 1112A is referred to herein as the “youngest” request station, and includes the youngest forward and reverse controllers, the youngest forward and reverse registers, and the youngest delay buffer. Similarly, request station 1112F is referred to herein as the “oldest” request station, and includes the oldest forward and reverse controllers, the oldest forward and reverse registers, and the oldest delay buffer.
The youngest forward register receives new memory transactions (MTIN) from switch crossbar 510. When a new memory transaction MTIN arrives in the youngest forward register, the youngest forward controller sets the validity bit VIN for the youngest forward register and places a tag TAGS from tag generator 1102 into the youngest forward register. In this description a bit is set by making it a logical one (“1”) and cleared by making it a logical zero (“0”).
When set, signal X indicates that the contents of forward register 1302 have been transmitted to a memory track 504.
Each forward controller 1114 generates a signal BOUT every transaction cycle where
BOUT=VBIN{overscore (X)} (1)
Each forward controller 1114 shifts into its forward register 1302 the contents of an immediately younger forward register when:
S=1 (2)
where
S={overscore (V)}+X+{overscore (BIN)} (3)
Referring to
The validity bit V for each forward register 1302 is updated each transaction cycle according to
V=V{overscore (X+SVIN)} (4)
Each forward controller 1114 copies TAGS, V, and M from its forward register 1302 into its delay buffer 1306 every transaction cycle. M is the address of the request station 1112. Each forward controller 1114 also copies X and S into its delay buffer 1306 every transaction cycle. Each delay buffer 1306 imposes a predetermined delay on its contents that is equal to the known predetermined time that elapses between sending a memory transaction to a memory track 504 and receiving a corresponding result from that memory track 504.
Each transaction cycle, an XDEL, VDEL, SDEL, MDEL, and TAGSDEL emerge from delay buffer 1306. XDEL is X delayed by delay buffer 1306. VDEL is V delayed by delay buffer 1306. SDEL is S delayed by delay buffer 1306. When XDEL is set, reverse register 1304 receives a result Result/N selected according to MDEL from a memory track 504, and a TAGSDEL, VDEL and SDEL from delay buffer 1306, the known predetermined period of time after sending the corresponding memory transaction from forward register 1302 to that memory track 504.
Each transaction cycle, reverse controller 1116 generates a signal GOUT where
GOUT=VDELGIN (5)
A reverse register 1304 sends its contents (a result ResultOUT and a tag TAGS) to switch crossbar 510 when
{overscore (VDEL)}GIN=1 (6)
Each reverse controller 1116 shifts into its reverse register 1304 the contents of an immediately younger reverse register when:
SDEL=1 (7)
The contents of each reverse register include a result Result, a tag TAGSDEL, and delayed validity bit VDEL. Referring to
Memory Arbitration
Each memory controller 532 controls a memory track 504 over a memory bus 534. Referring to
The SDRAMs 1406 within a memory track 504 operate in pairs to provide a double-wide data word. For example, memory bank 1408A in SDRAM 1406A provides the least-significant bits of a data word, while memory bank 1408E in SDRAM 1406B provides the most-significant bits of that data word.
Memory controller 532 operates efficiently to extract the maximum bandwidth from memory track 504 by exploiting two features of SDRAM technology. First, the operations of the memory banks 1408 of a SDRAM 1406 can be interleaved in time to hide overhead such as precharge and access time. Second, the use of autoprecharge makes the command and data traffic equal. For an SDRAM, an eight-byte transfer operation requires two commands (activate and read/write) and two data transfers (four clock phases).
During this eight-clock period, SDRAM 1406A receives a read command RD(A) at t5. SDRAM 1406A transmits the data A0, A1, A2, A3 requested by the read command during the two clock cycles between times t7 and t9. SDRAM 1406A receives another activation command ACT(A) at time t10.
Three other read operations are interleaved with the read operation just described. SDRAM 1406A receives an activation command ACT(B) at time t4. The activation command prepares bank 1408B of SDRAM 1406A for a read operation. The receipt of the activation command also begins an eight-clock period during which bank 1408B is not available to accept another activation.
During this eight-clock period, SDRAM 1406A receives a read command RD(B) at t7. SDRAM 1406A transmits the data B0, B1, B2, B3 requested by the read command during the two clock cycles between times t9 and t11.
SDRAM 1406A receives an activation command ACT(C) at time t6. The activation command prepares bank 1408C of SDRAM 1406A for a read operation. The receipt of the activation command also begins an eight-clock period during which bank 1408C is not available to accept another activation.
During this eight-clock period, SDRAM 1406A receives a read command RD(C) at t9. SDRAM 1406A transmits the data C0, C1, and so forth, requested by the read command during the two clock cycles beginning with t11.
SDRAM 1406A receives an activation command ACT(D) at time t8. The activation command prepares bank 1408D of SDRAM 1406A for a read operation. The receipt of the activation command also begins an eight-clock period during which bank 1408D is not available to accept another activation.
During this eight-clock period, SDRAM 1406A receives a read command RD(D) at t11. SDRAM 1406A transmits the data requested by the read command during two subsequent clock cycles in a manner similar to that describe above. As shown in
Each input port 550 associates a priority with each memory transaction based on the order in which the memory transactions were received at that input port 550 (step 1604). In one implementation priorities are associated with memory transactions through the use of forward queue 1104 described above. As memory transactions age, they progress from the top of the queue (request station 1112A) towards the bottom of the queue (request station 1112F). The identity of the request station 1112 in which a memory transaction resides indicates the priority of the memory transaction. Thus the collection of the request stations 1112 within an input port 550 constitutes a set of priorities where each memory transaction has a different priority in the set of priorities.
Arbiter 1206 generates a signal BNKRDY for each request station 1112 based on the availability to accept a memory transaction of the memory bank 1208 to which the memory transaction within that request station 1112 is addressed (step 1606). This information is passed to arbiter 1206 as part of the AGE signal, as described above. Each BNKRDY signal tells the request station 1112 whether the memory bank 1408 to which its memory transaction is addressed is available.
Arbiter 1206 includes a state machine or the like that tracks the availability of memory banks 1408 by monitoring the addresses of the memory transactions gated to memory controller 532. When a memory transaction is sent to a memory bank 1408, arbiter 1206 clears the BNKRDY signal for that memory bank 1408, thereby indicating that that memory bank 1408 is not available to accept a memory transaction.
After a predetermined period of time has elapsed, arbiter 1206 sets the BNKRDY signal for that memory bank 1408, thereby indicating that that memory bank 1408 is available to accept a memory transaction.
As described above, the BNKRDY signal operates to filter the memory transactions within request stations 1112 so that only those memory transactions addressed to available memory banks 1408 are considered by arbiter 1106 for presentation on internal bus 548. Also as described above, arbiter 1206 selects one of the memory transactions presented on internal bus 548 using a fairness scheme. Thus memory crossbar 512 selects one of the memory transactions for transmission over memory bus 534 based on the priorities and the bank readiness signals (step 1608). Finally, memory crossbar 512 sends the selected memory transaction over memory bus 534 to memory tracks 504 (step 1610).
Tag Generator
As mentioned above, the pair of tag generators associated with a bus are configured to independently generate the same tags in the same order. For example, tag generators 802 and 902 are associated with bus 522, and tag generators 1002 and 1102 are associated with bus 528.
In one implementation, the tag generators are buffers. The buffers are initialized by loading each buffer with a set of tags such that both buffers contain the same tags in the same order and no tag in the set is the same as any other tag in the set. In One implementation each buffer is a first-in, first-out (FIFO) buffer. In that implementation, tags are removed by “popping” them from the FIFO, and are returned by “pushing” them on to the FIFO.
In another implementation, each of the tag generators is a counter. The counters are initialized by setting both counters to the same value. Each tag is an output of the counter. In one implementation, the counter is incremented each time a tag is generated. If results return across a bus in the same order in which the corresponding memory transactions were sent across the bus, then the maximum count of the counter can be set to account for the maximum number of places (such as registers and the like) that a result sent across a bus and the corresponding memory transaction returning across the bus can reside.
However, if results do not return across a bus in the same order in which the corresponding memory transactions were sent across the bus, a control scheme is used. For example, each count can be checked to see whether it is still in use before generating a tag from that count. If the count is still in use, the counter is frozen (that is, not incremented) until that count is no longer in use. As another example, a count that is still in use can be skipped (that is, the counter is incremented but a tag is not generated from the count). Other such implementations are contemplated.
In another implementation, the counters are incremented continuously regardless of whether a tag is generated. In this way, each count represents a time stamp for the tag. The maximum count of each counter is set according to the maximum possible round trip time for a result and the corresponding memory transaction. In any of the counter implementations, the counters can be decremented rather than incremented.
In another implementation, depicted in
The read address (RA) of memory 1704 receives the count output of counter 1702. In this way, counter 1702 “sweeps” memory 1704. The data residing at each address is tested by a comparator 1706. A value of “1” indicates that the count is available for use as a tag. A value of “1” causes comparator 1706 to assert a POP signal. The POP signal causes gate 1708 to gate the count out of the tag generator for use as a tag. The POP signal is also presented at the write enable pin for port one (WE1) of memory 1704. The write data pin of port one (WD1) is hardwired to logic zero (“0”). The write address pins of port one receive the count. Thus when a free tag is encountered that tag is generated and marked “in-use.”
When a tag is returned to the tag generator, its value is presented at the write address pins for port zero (WA0), and a PUSH signal is asserted at the write enable pin of port zero (WE0). The write data pin of port zero (WD0) is hardwired to logic one (“1”). Thus when a tag is returned to the tag generator, that tag is marked “free.”
In another implementation, shown in
One of the rows is all logic zeros, indicating that no tags are free. Each of the other rows contains a single logic one, each row having the logic one in a different bit position. Any bits more significant than the logic one are logic zeros, and any bits less significant than the logic one are “don't cares” (“X”). Such a truth table for a 1×4 memory is shown in Table 1.
The read data from read port RD 1702 is applied to priority encoder 1806. If a tag is free, the output of priority encoder 1806 is used as the tag.
In the above-described implementations of the tag generator, a further initialization step is employed. A series of null operations (noops) is sent across each of busses 522 and 528. These noops do not cause the tag generators to generate tags. This ensures that when the first memory transaction is sent across a bus, the pair of tag generators associate with that bus generates the same tag for that memory transaction.
The invention can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Apparatus of the invention can be implemented in a computer program product tangibly embodied in a machine-readable storage device for execution by a programmable processor; and method steps of the invention can be performed by a programmable processor executing a program of instructions to perform functions of the invention by operating on input data and generating output. The invention can be implemented advantageously in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. Each computer program can be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language can be a compiled or interpreted language. Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory. Generally, a computer will include one or more mass storage devices for storing data files; such devices include magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM disks. Any of the foregoing can be supplemented by, or incorporated in, ASICs (application-specific integrated circuits).
A number of embodiments of the invention have been described. Nevertheless, it will be understood that various modifications maybe made without departing from the spirit and scope of the invention. Accordingly, other embodiments are within the scope of the following claims.
This application is a continuation of U.S. application Ser. No. 09/925,156, filed Aug. 8, 2001, which is incorporated herein by reference in its entirety for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 09925156 | Aug 2001 | US |
| Child | 11218963 | Sep 2005 | US |
