APPARATUS AND MECHANISM TO BYPASS PCIE ADDRESS TRANSLATION BY USING ALTERNATIVE ROUTING

Abstract

An address space field is used in conjunction with a normal address field to allow indication of an address space for the particular address value. In one instance, one address space value is used to indicate the bypassing of the address translation used between address spaces. A different address space value is designated for conventional operation, where address translations are performed. Other address space values are used to designate different transformations of the address values or the data. This technique provides a simplified format for handling address values and the like between different devices having different address spaces, simplifying overall computer system design and operation.

Description

BACKGROUND

1. Field

The field relates to transfers of information between various address spaces.

2. Description of the Related Art

Modern computers are extremely sophisticated, complicated and powerful. To improve the processing capabilities, many modern computers include intelligent input output (I/O) devices. These intelligent I/O devices often include a system-on-a-chip, which includes a microprocessor and has a connected memory. Of course, the computer includes its own main microprocessor and memory. The presence of multiple microprocessors often creates a situation of disparate address spaces between the various microprocessors. The intelligent I/O devices are often connected to the computer using advanced interfaces, such as Peripheral Component Interconnect Express (PCIe). PCIe includes its own address space, which is in addition to the address spaces of the various microprocessors. The existence of these plurality of address spaces in the past has required address translations at each step and in each direction. The many address translations complicated overall computer system design, often unnecessarily.

SUMMARY

An address space field is used in conjunction with the normal address field to allow indication of an address space for the particular address value. In one instance, one address space value is used to indicate the bypassing of the address translation used between address spaces. A different address space value is designated for conventional operation, where address translations are performed. Other address space values are used to designate different transformations of the address values or the data. This technique provides a simplified format for handling address values and the like between different devices having different address spaces, simplifying overall computer system design and operation.

BRIEF DESCRIPTION OF THE FIGURES

For a detailed description of various examples, reference will now be made to the accompanying drawings in which:

FIG. 1 is a block diagram of an example computer system.

FIG. 2 is a block diagram illustrating address translations according to the prior art.

FIG. 3 is a block diagram of an example system on a chip using address space values.

FIG. 4 is a block diagram of a PCIe port of the system on a chip of FIG. 3.

FIG. 5 is a block diagram of a second example system on a chip using address space values.

FIG. 6 is a block diagram of a switch in the second example system on a chip.

FIG. 7 is a detailed block diagram of the transmit portion of a PCIe port with a plurality of address spaces.

DETAILED DESCRIPTION

Referring now to FIG. 1, an example computer system 100 is illustrated. A PC or server mainboard or motherboard 102 is connected to an I/O card 104 using a PCIe link 106. The motherboard 102 includes a microprocessor 108 that includes an embedded PCIe root port 110 and a memory management unit (MMU) 112. Main memory 114 is connected to the microprocessor 108 and cooperates with the MMU 112. The MMU 112 provides the virtual address to physical address translations necessary for normal operation, where the computer system microprocessor 108 is operating in a virtual address space and needs to access the physical memory 114.

The I/O card 104 includes a semiconductor device that is a system on a chip (SOC) 116. The SOC 116 includes a microprocessor 118, which may include an MMU 119 (FIG. 3) and various integrated functions. A PCIe port 120 is used to connect to the motherboard 102. A direct memory access (DMA) controller 122 is used to control transfer of data between I/O card memory 124 and an I/O function 126. Exemplary I/O functions include disk array controllers, advanced network cards and the like. The DMA controller 122 handles transferring data between the I/O function 126 and memory 124 and between the memory 124 and the main memory 114 on the motherboard 102.

Referring now to FIG. 2, a block diagram illustrating the data transfers and address translations according to the prior art over a PCIe link are illustrated. A memory 214, similar to the memory 114 on the motherboard 102, contains a buffer 230 which contains data that is to be transferred to a buffer 232 in a memory 224, which is similar to memory 124. The data is to be moved from the buffer 230 over the PCIe link 206. The data is provided from the buffer 230 to a PCIe root port 210. A transmitter (TX) section 234 of the PCIe root port 210 receives the data and a translate block 236 translates the address from the physical address of the memory 214 to a PCIe address. The data is transmitted to an endpoint PCIe port 220, which is similar to the PCIe port 120. The data is received at a receive block 238, where a translate block 240 translates the address from the PCIe address to the physical address of the memory 224. The data is then placed in the buffer 232.

If the data is to be transferred from the buffer 232 to the buffer 230, then the data is retrieved from the buffer 232 and provided to a transmit block 242 in the PCIe port 220. The transmit block 242 includes a translate block 244 to translate from the physical memory address used with memory 224 to the PCIe address. The data is received at a receive block 246 in the PCIe root port 210. A translate block 248 translates the address from the PCIe address to the physical address of the memory 214 and then the data is deposited in the buffer 230.

As can be seen, multiple address translations are required even though the processors on each device are highly sophisticated and can manage very complicated memory maps. One difficulty is the need to program each of the particular translations into the various translate blocks. On the PCIe receive side, this is done through base address registers (BARs), of which there are a limited number and must be programmed or reprogrammed as needed. On the PCIe transmit side, the direct address translations are programmed or reprogrammed as necessary.

Referring now to FIG. 3, a detailed block diagram of the SOC 116 is provided. The microprocessor 118, a memory controller 123 connected to the memory 124, the DMA controller 122 and the PCIe port 120 are interconnected by a crossbar or switch array 302. An address format is provided for each of the connections to the switch array 302. The address format is divided into two portions, a pre-pended address space value or ASEL portion and a basic memory address portion, such as a Axx-A00, for example A31-A00 or A63-A00. The switch array 302 is designed to handle the pre-pended address space value bits in addition to the normal address bits, as well as the normal data and control bits. In the illustrated example, an ASEL bit for the memory controller 123 and the microprocessor 118 is zero, which is used to indicate conventional operation. The PCIe port 120 and DMA controller 122 can set the ASEL bit as desired to indicate conventional operation or operation in a secondary address space. By setting the ASEL bit to a one value, operation in the secondary address space is indicated. The address value used on the PCIe link is the normal PCIe address value without any address space value selection bits.

In operation, the DMA controller 122 is programmed for a particular data transfer. As an example, for a transfer of data from a buffer in the memory 124 to the PCIe port 120, the DMA controller 122 is programmed to provide an ASEL value of zero when reading the data from the memory 124 and is programmed to use an ASEL value of one when writing the data to the PCIe port 120 if no address translation is to be performed. If address translation is to be performed, then the DMA controller 122 is programmed to use an ASEL value of zero on the write operation. If the microprocessor 118 is operating directly with the PCIe port 120, then an ASEL value of zero is used as in the example the microprocessor 118 only provides memory operations using a zero ASEL value. In that instance, the PCIe port 120 performs address translations as normally done.

Referring now to FIG. 4, details of the PCIe port 120 are provided. A bus master module 402 is provided to connect to the switch array 302. A PCIe core 404 is provided to develop the PCIe link, such as to the motherboard 102. A transmit address path 406 from the bus master module 402 is provided to the input of a 2 bit demultiplexer 408. The selection output of the demultiplexer 408 is provided by the ASEL bit in the address provided over the transmit address path 406. The zero or normal address space value output of the demultiplexer 408 is provided to a translate block 410, which translates the memory 124 physical addresses to PCIe addresses as in the prior art. The output of the translate block 410 is provided as the zero input to a multiplexer 412. The output of the multiplexer 412 is provided to the PCIe core 404 as the transmit address. The one or alternate address space value output of the demultiplexer 408 is provided directly to the one input of the multiplexer 412. By this direct connection, no address translations are performed on the address in the particular transaction. The ASEL bit is stripped off or removed by either the multiplexer 412 or the PCIe core 404.

In the illustrated example, a receive (RX) address path 414 is provided from the PCIe core 404 to the input of a demultiplexer 416. The output control of the demultiplexer 416 is provided by an address map block 418 which examines the address bits, such as Axx-A00, of the transaction and appropriately determines whether the addresses need to be translated or can be used in an untranslated format. If translation is required, the zero output from the demultiplexer 416 is provided to a translate block 420, which performs the necessary address translation. The output of the translate block 420 is provided to a zero input of a multiplexer 422, with a zero value ASEL bit pre-pended to the address. The output of the multiplexer 422 is provided as the receive address to the bus master module 402.

If no address translation is required, the one output of the demultiplexer 416 provides the address directly to the one input of the multiplexer 422, with a one value provided as the pre-pended ASEL bit. By providing the ASEL bit at the multiplexer 422, the internal routing inside the SOC 116 can be done using the ASEL bit as illustrated in FIG. 3.

In another example, the untranslated or bypass path is not present in the receive path and address translations based on the base address registers (BARs) are performed. In this example the demultiplexer 416, multiplexer 422 and address map 418 used with the demultiplexer 416 are not present and an ASEL value of zero is always used.

FIG. 5 provides a second example of an SOC 116′. Like components with the SOC 116 of FIG. 3 are numbered the same. The difference in the case of FIG. 5 is that an alternate switch array 302′ is provided which has separate connections to a PCIe port 120′ for address values with an ASEL value of zero and an ASEL value of one. In this example the PCIe port 120′ does not need to do the demultiplexing with the demultiplexer 408 or multiplexing using the multiplexer 422 but rather the paths are provided directly to the two connections of the switch array 302′. The switch array 302′ uses the ASEL bit as an additional routing term when routing messages. Thus, effectively the PCIe port 120′ has two connections into the switch array 302′ rather than the single connection as illustrated in FIGS. 3 and 4.

Referring now to FIG. 6, a switch array 302″ is provided. In the switch array 302″, the multiplexer, demultiplexer and translate blocks that were illustrated in FIG. 4 have been moved into the switch array 302. The switch array 302″ includes a crossbar core 602, which is effectively the switch array 302. One port 604 includes the multiplexer, demultiplexer and translation logic as present in FIG. 4. Like element numbers from FIG. 4 are provided in FIG. 6 with the addition of a double prime to indicate this example use in the switch array 302″. By integrating the multiplexer, translation and demultiplexer elements into the switch array 302″, conventional PCIe port logic that does not include the multiplexer, demultiplexer and translate elements can be utilized. As the above examples are integrated onto an SOC, the location of these elements is thus a design choice as functionally they are equivalent.

The above description uses a single ASEL bit to simplify the description. In another example shown in FIG. 7, the address space value indication is provided by a four bit ASEL field. Instead of the two address space values as done using a single ASEL bit, use of four bits provides up to 16 separate address space value indications. The bus master module 702 provides the address values to the input of a 16 output address demultiplexer 704. The four ASEL bits are utilized to select the desired output of the address demultiplexer 704. As in the prior example, an ASEL value of zero is utilized to provide address values to a translate block 0 706, which provides prior art type address translation. The ASEL one output is provided directly to an address multiplexer 708 without any translation as illustrated in FIG. 4. As illustrated, an ASEL value of 2 directs the output of the address demultiplexer 704 to an address translate block 2 710, which can be bypassed by a switch 712. The selection of the translate block 2 710 or bypassing switch 712 is performed by a configuration register bit to allow selective translation or bypassing of address translation. The output of the address translate block 2 710 and bypass switch 712 is provided to the address multiplexer 708. Similar address translation blocks and bypass switches are provided at the remaining outputs of the address demultiplexer 704 up to an output representing the value F or 15, whose output is provided to an address translation block F 714 and a bypass 716. The outputs of the address translation blocks 2 to F and related bypass switches are provided to respective inputs of the address multiplexer 708.

Data paths were not illustrated in FIG. 4 as the data path was straight through, with no data manipulations. In FIG. 7, data path manipulations are provided. A data path 718 is provided from the bus master module 702 to the input of a 16 output data demultiplexer 722. The selection of the data demultiplexer 722 is provided by the ASEL bits. Thus the outputs of the address demultiplexer 704 and the data demultiplexer 722 are matched so that the steering of the address and data values are done based on the same ASEL value. In the illustrated example, the zero and one outputs from the data demultiplexer 722 go directly to the zero and one inputs of a data multiplexer 724, whose output is the data path to a PCIe core 720. The two output of the data demultiplexer 722 is provided to an endian reversal block 726 to allow conversion between big endian and little endian systems. Noting that the two output path through the data demultiplexer 722 to the endian reversal block 726 to the data multiplexer 724 parallels the address translate block 2 710 or bypass switch 712, address translations can be used if desired in addition to the data endian conversion or address translation can be omitted while endian conversions are performed. The illustrated example F or 15 output of the data demultiplexer 722 is provided to a compression block 728 whose output goes to the F or 15 input of the data multiplexer 724. As with the endian conversion, the address path allows for address translations or direct untranslated addresses depending upon the particular design requirements. Various desired data manipulations can be selected using other outputs as desired. The endian reversal and compression data conversions are illustrative and not exhaustive.

While FIG. 7 does not show the receive path for the address or data, the receive path is configured similarly to the address receive path shown in FIG. 4 except for the inclusion of the data path operations and the 16 alternative address spaces rather than just two.

The above description has focused on an endpoint PCIe port configuration. It is understood that the use of the additional bits to provide address space value indications which are used to indicate different functions can be used in a PCIe root port configuration as well.

The above description has described the ASEL bits as pre-pended to the normal address bits. The pre-pending is done for illustrative purposes. It is understood that the ASEL bits can be post-pended or can be provided in a side channel if desired.

While configuration and operation is described using a PCIe port as exemplary, it is understood that selections based on address space value bits can be done for many different functions, functions that need some processing of address or data values between the source and destination. As one example, inclusion in and operation with a HyperTransport interface is similar to the exemplary PCIe port. Other address translation examples include various remote DMA (RDMA) protocols. Endian conversion and compression were described as data operations but other data operations can also be done, such as encryption and the like.

It is understood that different ports or functional blocks can use different address and data transformations in the same system. For example, address translation bypassing can be used with a PCIe port and data encryption can be used with a disk array function by assigning each operation to a different address space, such as zero for normal PCIe port and serial attached SCSI (SAS) port operation, one for PCIe port address translation bypassing and two for SAS port data encryption. In such a case, the multiplexers and demultiplexers at each port do not need to be complete, that is include all outputs or inputs for the number of address space value selection bits, but can only decode for address space values relevant to the particular function, with any other address space value at that port generating an error condition.

While the above description has focused on configurations and operation internal to an SOC, it is understood that the configurations and operation apply equally to external connections.

While only the DMA controller and the PCIe port have been described as providing and using different ASEL bit values in their operations, it is understood that any other device can use address space values if desired. For example, the MMU in the processor can be extended to add ASEL bits to its operation to allow the processor to perform address space indication as well.

By providing address space value selection bits in addition to normal address bits, different functionalities for the different address spaces can be specified, allowing improved operation of the resulting computer.

The above description is intended to be illustrative, and not restrictive. For example, the above-described examples may be used in combination with each other. Many other examples will be upon reviewing the above description. The scope should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.”

Claims

1. A device comprising: an interface that includes: an input configured to receive a first address;a memory configured to store an address map; andan output configured to provide a second address based on the first address and an indication of an address space of the second address, wherein the interface is configured to determine the address space of the second address based on the first address and the address map.

2. The device of claim 1 wherein: the interface further includes an address space translator coupled to the input and the output; andthe interface is configured to determine whether to cause the address space translator to translate the first address to produce the second address or whether to cause the first address to be provided as the second address based on the first address and the address map.

3. The device of claim 2, wherein the interface is configured to cause the indication of the address space to have a first value when the address space translator translates the first address to produce the second address and to have a second value when the first address is provided as the second address.

4. The device of claim 2, wherein the interface includes a demultiplexer that includes an input coupled to the input of the interface, a first output coupled to the address space translator, and a second output coupled to the output of the interface such that the address space translator is bypassed.

5. The device of claim 4, wherein the interface includes a multiplexer that includes a first input coupled to the address space translator, a second input coupled to the second output of the demultiplexer and an output coupled to the output of the interface.

6. The device of claim 1, wherein the interface is a Peripheral Component Interconnect Express (PCIe) interface.

7. The device of claim 1 further comprising: a switch array coupled to the output of the interface; anda destination device coupled to the switch array and configured to receive the second address and the indication of the address space of the second address.

8. The device of claim 7, wherein the destination device is from a group consisting of: a direct memory access circuit, a processor, and a memory controller.

9. The device of claim 1, wherein: the input of the interface is configured to receive a first set of data;the interface is configured to perform a function on the first set of data to produce a second set of data;the function is based on the address space of the second address; andthe output of the interface is configured to provide the second set of data with the second address and the indication of an address space of the second address.

10. The device of claim 9, wherein the function includes at least one of: compression, conversion from big endian mode to little endian mode, or conversion from little endian mode to big endian mode.

11. A device comprising: a processor associated with an address space; andan interface that includes: an input configured to receive a first address; andan output coupled to the processor and configured to provide a second address based on the first address and an indication of whether the second address is associated with the address space of the processor.

12. The device of claim 11, wherein the interface includes an address space translator and is configured to determine whether to: utilize the address space translator to translate the first address to produce the second address and cause the indication to specify that the second address is associated with the address space of the processor; orprovide the first address as the second address and cause the indication to specify that the second address is not associated with the address space of the processor.

13. The device of claim 12, wherein the interface includes a demultiplexer that includes an input coupled to the input of the interface, a first output coupled to the address space translator, and a second output coupled to the output of the interface such that the address space translator is bypassed.

14. The device of claim 13, wherein the interface includes a multiplexer that includes a first input coupled to the address space translator, a second input coupled to the second output of the demultiplexer and an output coupled to the output of the interface.

15. The device of claim 11, wherein the interface is a Peripheral Component Interconnect Express (PCIe) interface.

16. The device of claim 11 further comprising a memory controller coupled to the output of the interface, wherein the memory controller is associated with the address space.

17. A method comprising: receiving, by an interface, a first address;determining, by the interface, based on the first address, whether to translate the first address to produce a second address or to provide the first address as the second address; andproviding, by the interface, the second address and an indication of an address space of the second address to at least one of: a processor, a memory controller, or a direct memory access circuit.

18. The method of claim 17, wherein: the processor and the memory controller are associated with a first address space; andthe method further comprises: translating the first address to produce the second address based on the first address space; andbased on the translating, causing the indication to specify that the address space of the second address is the first address space of the processor and the memory controller.

19. The method of claim 17 further comprising: translating the first address;receiving the translated first address at a first input of a multiplexer;receiving the first address at a second input of the multiplexer; andproviding, via the multiplexer, either the translated first address or the first address as the second address.

20. The method of claim 17, wherein the interface is a Peripheral Component Interconnect Express (PCIe) interface.