US7155602B2 - Interface for integrating reconfigurable processors into a general purpose computing system - Google Patents
Interface for integrating reconfigurable processors into a general purpose computing system Download PDFInfo
- Publication number
- US7155602B2 US7155602B2 US10/011,835 US1183501A US7155602B2 US 7155602 B2 US7155602 B2 US 7155602B2 US 1183501 A US1183501 A US 1183501A US 7155602 B2 US7155602 B2 US 7155602B2
- Authority
- US
- United States
- Prior art keywords
- command
- data
- comlist
- execution
- command list
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/76—Architectures of general purpose stored program computers
- G06F15/78—Architectures of general purpose stored program computers comprising a single central processing unit
- G06F15/7867—Architectures of general purpose stored program computers comprising a single central processing unit with reconfigurable architecture
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/24—Resetting means
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/38—Concurrent instruction execution, e.g. pipeline, look ahead
- G06F9/3877—Concurrent instruction execution, e.g. pipeline, look ahead using a slave processor, e.g. coprocessor
- G06F9/3879—Concurrent instruction execution, e.g. pipeline, look ahead using a slave processor, e.g. coprocessor for non-native instruction execution, e.g. executing a command; for Java instruction set
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/38—Concurrent instruction execution, e.g. pipeline, look ahead
- G06F9/3885—Concurrent instruction execution, e.g. pipeline, look ahead using a plurality of independent parallel functional units
- G06F9/3893—Concurrent instruction execution, e.g. pipeline, look ahead using a plurality of independent parallel functional units controlled in tandem, e.g. multiplier-accumulator
- G06F9/3895—Concurrent instruction execution, e.g. pipeline, look ahead using a plurality of independent parallel functional units controlled in tandem, e.g. multiplier-accumulator for complex operations, e.g. multidimensional or interleaved address generators, macros
- G06F9/3897—Concurrent instruction execution, e.g. pipeline, look ahead using a plurality of independent parallel functional units controlled in tandem, e.g. multiplier-accumulator for complex operations, e.g. multidimensional or interleaved address generators, macros with adaptable data path
Definitions
- the present invention relates to a method and system for interfacing computer processors.
- the present invention relates to a computer system interface that provides for the integration of reconfigurable processors with instruction processors and other reconfigurable processors.
- Typical computing systems generally include traditional instruction processors for processing and controlling the instructions and data flow of a typical computer program.
- Computer instructions can also be implemented with hardware logic.
- Hardware logic-implemented functions can greatly accelerate the processing of application algorithms over those same algorithms implemented in software. Sections of code such as compute-intensive algorithms, and/or repetitious instructions can benefit from hardware implementation.
- computer instructions implemented in hardware logic run much faster than those implemented in software, hardware logic is much more expensive to design, develop, and manufacture than an average computer application.
- the computer code is divided into sections, generally during compilation. Depending on optimization requirements these sections of code can then be processed by one or more instruction processors, and/or one or more reconfigurable processors.
- Performance enhancements resulting from reconfigurable computing can provide orders of magnitude improvements in speed for a wide variety of computing code.
- the coordination between the instruction processors, reconfigurable processors, main memory, and various other components can degrade these performance improvements.
- the increased number of components necessary to coordinate such a hybrid computer system can add significantly to the overall cost.
- the present invention is directed to an interface for integrating reconfigurable processors with standard instruction processors and/or other reconfigurable processors into a computer system that substantially obviates one or more of the problems due to limitations and disadvantages of the related art.
- the present invention includes an interface control processor, storage for the interface instructions, data registers, flag registers, user registers, and a direct memory access (“DMA”) processor.
- interface control processor storage for the interface instructions
- data registers storage for the interface instructions
- flag registers flag registers
- user registers storage for the interface instructions
- DMA direct memory access
- the reconfigurable processor interface is an active interface.
- the interface takes direction from instruction processors, reconfigurable processors, as well as the user logic within a reconfigurable processor, yet is capable of control and decision making on its own.
- This active control is defined through a coordinated effort of the various interface registers, specific areas of common memory, the dedicated reconfigurable processor memory, and the user logic of the reconfigurable processor with an interface control program.
- An object of the present invention is to provide a mechanism by which the instruction processors communicate and coordinate with arbitrary user logic in reconfigurable processors.
- Another object of the present invention is to provide an active control that allows instruction processors and reconfigurable processors to function autonomously.
- Another object of the present invention is to provide a means for moving memory contents between common memory and the dedicated memory of a reconfigurable processor.
- a further object of the present invention is to provide a flexible interface that can be defined for arbitrary instruction processor instruction sequences and arbitrary reconfigurable user logic.
- Another object of the present invention is to ensure the protected operation of the interface by ensuring that the memory to be referred to is only within the boundaries of a user program.
- Another object of the present invention is to provide interaction with a user program without requiring operating system services.
- Yet a further object of the present invention is to provide a means for the reconfigurable processor to interact with input/output services.
- Another object of the present invention is to divide application programs among instruction processors and reconfigurable processors to achieve optimum performance.
- Another object of the present invention is to allow a single-system image to be constructed for a hybrid system of instruction processors and reconfigurable processors.
- Another object of the present invention is to allow a single-system image to be constructed for a system of purely reconfigurable processors.
- a further object of the present invention is to allow the construction of a cluster of Symmetric Multi-Processor (“SMP”) hybrid nodes or strictly instruction nodes, or reconfigurable processor nodes, or various combinations thereof.
- SMP Symmetric Multi-Processor
- Still a further object of the present invention is to allow instruction processors and reconfigurable processors to be integrated into a single-system image SMP architecture system.
- a further object of the present invention is to allow reconfigurable processors to be integrated into a single-system image SMP.
- Another object of the present invention is to allow the user logic of the reconfigurable processor to coordinate with the rest of a single-system image SMP system.
- the interface for integrating reconfigurable processors into a general purpose computing system provides the ability to coordinate the execution of an application that combines processor code and synthesized logic.
- the present invention provides an interface for integrating reconfigurable processors into a general purpose computing system.
- the interface includes: (1) interface control processor for managing the interaction between the at least one reconfigurable processor and the computer system; (2) interface control processor instructions organized into command lists; (3) random access memory for storing the current command list; (4) registers for storing data and settings; (5) common memory; (6) direct memory access logic for coordinating the transfer of the reconfigurable processor instructions and data; (7) address translation buffer for storing translation data and translating virtual memory addresses to physical memory addresses; and (8) dedicated memory.
- the present invention provides a method for processing interface control processor instructions compiled from a user application.
- This method includes the steps of: (1) storing command lists in a dedicated area of common memory, (2) receiving a fetch command sent by the user application; (3) fetching a command list from the dedicated area; (4) loading the command list into a command list memory within the interface; (5) processing the command list through an interface control processor; (6) interacting with user logic to exchange data and control signals, and (7) determining if another command list is ready for processing, if so, processing the new command list; otherwise, waiting for another fetch command.
- FIG. 1 is a simplified, high level, functional block diagram of a multiprocessor computer architecture, including reconfigurable processors.
- FIG. 2 is a representational diagram of a reconfigurable processor used according to a preferred embodiment of the present invention.
- FIG. 3 is a flow diagram of the method of halting the instruction processing of a reconfigurable processor.
- FIG. 4 is a flow diagram of the method of restarting the execution of a reconfigurable processor after it has been halted.
- FIG. 5 is a representational diagram of a common memory organization according to a preferred embodiment of the present invention.
- FIG. 6 is a flow diagram of the method of processing interface control processor instructions.
- the present invention integrates a computer's instruction processors, common memory, and reconfigurable processors, referred to in the preferred embodiment as Multi-Adaptive Processors (“MAPs”).
- MAPs Multi-Adaptive Processors
- FIG. 1 an overview of the computer system incorporating MAPs 12 is shown.
- the instruction processor boards 10 and MAPs 12 reside on the trunk 20 and 22 to the crossbar 16 .
- the MAPs are connected via a multiplexer 14 .
- the crossbar 16 is then connected to common memory 18 through memory trunk 26 .
- Further embodiments of the present invention allow for placing the instruction processor 10 and/or the MAPs 12 in any other location, including, but not limited to, the memory trunk 26 , crossbar switch 16 , common memory inter-connect, or I/O bus 28 .
- the instruction processors 100 and MAPs 12 may also be on the same or separate circuit boards, or even integrated on the same computer chip.
- a MAP 12 is a standalone processing unit executing independently of instruction processors during normal operation, as well as while loading and storing data.
- Each MAP 12 incorporates various hardware components of the preferred embodiment of the present invention, including for purposes of illustration only, an interface control processor, referred to as a command processor 42 , command list memory 43 , a direct memory access (“DMA”) controller 44 , a translation look-aside buffer (“TLB”) 45 , data registers 46 , user data registers 48 , flag registers 47 , and on-board memory 50 .
- an interface control processor referred to as a command processor 42
- command list memory 43 a direct memory access (“DMA”) controller 44
- TLB translation look-aside buffer
- Each MAP 12 also includes user-configured logic known as the user array 60 .
- the user array of the present example contains two large Field Programmable Gate Arrays (“FPGAs”), referred to as user logic (“U_Logic”) 62 1 – 62 2 .
- FPGAs Field Programmable Gate Arrays
- U_Logic user logic
- During compilation the sections of code determined to be suitable for optimization through a hardware implementation, such as discrete algorithmic sections, are segregated out of the program code.
- the algorithmic sections of code from the application program are converted to provide hardware logic circuits within the user logic 62 1 – 62 2 .
- the command processor 42 processes commands, makes control decisions, and manages the transfer of data.
- a ComList is also generated during compilation of the user application.
- a ComList is used for controlling a MAP 12 or MAPs 12 1 – 12 N ( FIG. 1 ) during normal operation.
- the ComList contains a list of controlling instructions for the MAP's command processor 42 and is initially stored in common memory 18 ( FIG. 1 ) until it is fetched by the MAP's controller 40 into the ComList memory 43 .
- Data registers 46 consist of thirty-two, 64-bit registers known as DR 0 through DR 31 . These registers are generally used to hold addresses for both common memory 18 ( FIG. 1 ) and on-board memory 50 ; however, they can hold any needed data.
- data registers 46 scalar data can be sent to or received from the user array 60 . Simple arithmetic operations, as well as bitwise logic, are supported on these registers. The data register contents can be tested for zero/non-zero; therefore, tests together with branches provide support for loops.
- the bits of DR 0 are always 0/clear and the lower order bit of DR 1 is always 1/set. DR 0 contains integer 0 and DR 1 contains integer 1. Neither register can be overwritten.
- User data registers 48 are thirty-two registers of 64 bits known as UDR 0 through UDR 31 . User data can be sent directly from the ComList to the user array 60 without going through the data registers 46 . A group of user data registers 48 can be loaded from the ComList. When the last user data register of the group is loaded the user array 60 is interrupted. The user array 60 must understand the protocol by which user data registers 48 need to be read.
- Flag registers 47 are thirty-two single-bit registers FR 0 through FR 31 . Commands can test and wait on the state of flag registers 47 before execution. Commands can change the state of flag registers 47 , forcing them set and clear. In addition, there are logical instructions that allow combining flag states (AND, OR, XOR). Other commands allow testing and branching on their contents. For control purposes FR 0 is always 0/clear and FR 1 is always 1/set. Neither of these registers can be overwritten.
- the purpose of the flag registers 47 is to support coordination between different operations.
- the user logic can coordinate loading and executing a new ComList by setting a specified flag register.
- a command can test the flag register and then branch to the end of the ComList, indicating that the next ComList may be loaded.
- the user logic can coordinate movement of data in or out of on-board memory 50 using flag registers and data registers.
- a DMA instruction can be held waiting for a flag register to be set.
- the user logic can write addresses and length into data registers, and then set a specified flag register, allowing the DMA instruction to execute the movement of data.
- another flag register can be set to indicate to the user logic that data movement is complete.
- An additional register visible in the MAP is the ComList pointer 49 . This register is saved as part of the MAP status and indicates the index of the next command dispatched in the active ComList. When a MAP is halted the pointer indicates the next command to be executed if execution is restarted.
- On-board memory 50 consists of six banks of dual port 512K ⁇ 64-bit static random access memory (“RAM”) providing a total of 24 MB of available memory. Both the DMA controller 44 and the command processor 42 communicate with the on-board memory 50 via the six control-side ports 52 . The user array 60 communicates with the on-board memory 50 through the six user-side ports 54 .
- RAM static random access memory
- the user array 60 portion of a MAP 12 is configured as a hardware implementation of the algorithmic requirements of the user application.
- the user array 60 reads from, and writes to, on-board memory 50 through six user-side ports 54 and can interact with the control logic and the DMA controller 44 .
- DMA operations within the interface of a MAP 12 run more or less independently of processing within a user's logic. Coordination between these control streams is through the use of the flag registers 47 , data registers 46 and user data registers 48 .
- the DMA controller 44 is initiated by a DMA ComList instruction.
- the user array 60 writes an address and length into the data registers 46 and sets a flag register 47 .
- the ComList awaits the user array's signal, setting of the flag register, and then executes a DMA instruction that references the data registers 46 that have been setup by the user array.
- the DMA controller 44 can then signal its completion by setting or clearing a flag register 47 that the user array is monitoring.
- the FPGAs, user logic 62 1 and 62 2 , of the user array 60 are configured during a fetch configuration command from data in common memory and not from an on-board programmable read only memory (“PROM”).
- User logic 62 1 and 62 2 communicate between themselves using three dedicated 64-bit data buses 66 without using any memory bandwidth.
- MAP modules can also be connected together via a chaining data bus 64 . Through the use of chaining ports 64 a particular MAP can send partial results to another MAP, or similarly, can receive such partial results from another MAP.
- the user array 60 provides all logic for the chaining ports 64 .
- the chaining ports 64 use Double Data Rate (“DDR”) protocol that allows each data line to carry two bits of information. This provides for two chain input ports and two chain output ports. In an alternate embodiment without a DDR protocol only single input and output ports would be available on each MAP.
- DDR Double Data Rate
- MAPs 12 0 – 12 N can send interrupts to processors and can also receive a limited set of commands directly from the processors. Commands received directly from other processors, which are not fetched and executed from a MAP's ComList, are called direct commands. Interrupts are sent by a MAP 12 to a given processor in a twelve bit serial stream along with twelve source synchronous clock pulses.
- FR 31 provides a specific system interrupt mechanism.
- MAP status is stored in its status and control area and an interrupt is generated. This status operation is conditional on an interrupt enable flag taken from a control word in the status and control area. In all cases, if FR 31 sets, MAP execution attempts to halt. For this reason, internally 10 detected errors set FR 31 .
- a Stop switch is provided to add flexibility with handling interrupts sent to a MAP.
- a MAP will run with Stop enabled. This mode allows execution to halt when the MAP is interrupted.
- a MAP can run in a Stop disabled mode, providing the MAP with the ability to continue execution of a program, even when it has been interrupted.
- Stopping/halting MAP execution can result from several sources. In all cases this requires setting or attempting to set FR 31 . When there is an attempt to set FR 31 either directly, or indirectly, and Stop is enabled, execution of the MAP is halted.
- the MAP can be interrupted in the following situations: (1) a direct Stop command is received from a processor, (2) FR 31 is set from the ComList, (2) FR 31 is set from the user logic, or (4) the command processor detects an error, such as an address exception, page or memory fault, or some other internal fault.
- Stop enabled the following occurs: MAP control logic comes to the most graceful halt it can, waiting for execution logic to go quiet step 200 .
- the control state is saved in on-board memory addresses 0–31 step 210 .
- Status is stored into the MAP's status and control area of common memory step 220 .
- the MAP's TLB registers are stored into the TLB area step 230 .
- step 240 If a direct stop command was received step 240 the MAP is stopped step 242 , otherwise if interrupts are enabled step 250 , an interrupt is sent step 260 and the MAP unit halts step 270 . If Stop is disabled step 250 , the sequence above is executed except that in the last step the command that caused the error is abandoned and execution continues step 252 .
- any necessary changes to the MAP's parameters in the status and control area are made, including the TLB entries step 300 .
- If continuing execution of the instruction that caused the halt reload all saved parameters step 312 and then Continue from Saved step 314 .
- the direct command Continue can be sent to the MAP step 322 .
- a new sequence is to be started (for example, a new user or the current user with different commands)
- the proper command sequence must be stored in ComList step 332 , then direct commands are made to load parameters step 334 and Start execution step 336 .
- MAPs are actively controlled through the interface control program.
- the components of the interface control program include a pair of ComList pages 72 1A 14 72 1B located in the ComList area 70 of common memory 18 , a status and control page 82 1 , located in the status and control area 80 in common memory 18 , which holds status and control information and TLB data. Additional components, which coordinate to provide interface control, include the data registers 46 , user data registers 48 , flag registers 47 , on-board memory 50 , TLB 45 and user array 60 .
- the MAPs interface is controlled by commands in the ComList or direct commands issued by an instruction processor or another MAP.
- an application generates code for the standard instruction processor, ComLists for the MAP's interface, and hardware logic for the MAP's user array.
- ComLists are generated by the user application in order to coordinate data movement and control between the application code running in the instruction processor, and application logic running in the MAP's user array.
- Commands in the ComList correspond directly to instructions in a reduced instruction set computer (“RISC”) processor. These instructions are a small set of simple instructions for moving data, testing conditions, and branching.
- FPGA control processors can be reconfigured to function with various instruction sets, depending upon implementation needs.
- Each MAP 12 ( FIG. 2 ) is provided with two 4-KB ComList pages 72 A and 72 B from the ComList area 70 in common memory 18 providing a maximum useable space for each ComList of 512 words.
- Each ComList page is identified through a unique MAP ID number.
- the address of the ComList pages 72 1A , 72 1B through 72 NA , 72 NB are specified in conjunction with the ID number of the associated MAP 12 .
- Starting at relative address 0K in each MAP's ComList page 72 A+B is the first command list, ComList 0 72 A , for that MAP.
- the second command list, ComList 1 72 B is located at address 4K of that MAP's ComList area 72 A+B .
- Two ComList pages 72 A and 72 B are used to allow each MAP to work from one ComList page while the application software is loading the other ComList page. By swapping ComList pages the latencies of the processor and DMA are significantly reduced.
- the first word in each ComList is the ComList Length Command that defines the total number of command words in the buffer. For example, if there were only one additional command in the ComList, the first word, the Length Command, would have the value 2. This indicates that the ComList contains the length command word plus one additional command word.
- the application software loads a ComList into an available ComList page, ComList 0 or ComList 1 , of common memory step 400 , when ComList 0 or ComList 1 is ready to be processed the instruction processor sends a corresponding direct instruction, Fetch 0 or Fetch 1 , to the command processor step 410 .
- the ComList is fetched from common memory step 420 .
- the DMA only transfers enough cache lines to read all of the active ComList 0 .
- the complete ComList is stored in the ComList memory area 43 ( FIG. 2 ), RAM set aside specifically for the ComList, of the control logic step 430 . Placing the ComList in RAM allows the command processor 42 ( FIG. 2 ) to execute ComList loop instructions.
- the ComList commands can only loop within one ComList and not from one ComList to another.
- a FETCHDONE signal is provided to the MAP command processor 42 ( FIG. 2 ) and the ComList is executed step 440 .
- Each ComList is a maximum of 496 words in length, reserving the upper portion of the ComList memory area 43 ( FIG. 2 ) for bringing in 8 status and control words.
- a Fetch 0 or Fetch 1 direct command can be issued prior to completion of the current ComList, queuing up the next ComList.
- the command processor 42 FIG. 2
- the command processor 42 FIG. 2
- the command processor 42 checks for the availability of another ComList step 450 . If another ComList is ready it is processed in the same manner as the preceding ComList, otherwise the MAP 12 ( FIG. 2 ) awaits further instructions step 460 .
- command processor 42 begins executing a ComList that has a length of over 496, an error interrupt and halt will be generated.
- commands are executed sequentially unless the sequence is changed with a branch or is halted. Commands are available to set addresses, do DMA functions, branch and loop within a ComList, control and send parameters to the user array, etc.
- ComList commands are either 8 bytes or 16 bytes long. All commands, except certain direct commands, are fetched by the DMA controller 44 ( FIG. 2 ) from the ComList pages 72 A+B ( FIG. 5 ) in common memory 18 ( FIG. 5 ) and executed by the command processor 42 ( FIG. 2 ).
- command processor 42 executes the last command in the ComList space, and it is not a taken branch, execution stops.
- a direct command of Fetch 0 or Fetch 1 is required to restart execution. If a Halt command is executed in a ComList sequence either a Start or Continue direct command is required.
- An interrupt is conditionally generated if MAP execution halts.
- the data fields in the first 8 bytes of a ComList command are structured in the following manner:
- bit 63 00 field size code a b c d e f aa bb cc dd ee ff gg hh width 2 4 1 1 1 1 1 1 5 5 5 5 5 5 5 12 10
- the ComList Length Command is the first command in each ComList and is always located at address 0 of the ComList.
- the Length Command provides the total number of command and immediate data words contained in that particular ComList.
- the value in field (hh) may range from 2 to 496 words. A value of 2 would indicate that only the ComList Length Command is present plus one command word.
- a value of 496 is the max number of command words that can be used in the buffer. This max limit allows scratchpad room at the top of the 512-word buffer for status and control information.
- Direct Memory Access Commands move data between common memory 18 ( FIG. 1 ) and a MAP's on-board memory 50 ( FIG. 2 ). Data is always moved to and from common memory 18 ( FIG. 1 ) in a stride-1 fashion: linearly with all bytes referenced.
- Stride or gather/scatter address sequences can be specified as on-board memory addresses.
- the stride or gather/scatter address offsets are sized indexes. This means that stride or gather/scatter indexes are multiplied by the operand stream data size (8 bytes) before being added to a specified base address. Stride and gather/scatter indexes can be negative. Overflow will not be detected.
- the index list is taken from on-board memory 50 ( FIG. 2 ).
- Data in on-board memory can have the address reference sequence specified with a stride or with a sequence of gather/scatter addresses.
- the register DRee defines the stride and the format of the stride definition is as follows:
- the modulus field controls the number of banks in the bank sequence.
- a zero modulus indicates one bank in the bank sequence.
- a value 15 indicates a 16 bank sequence.
- the bank sequence has 16 fields of bank numbers. The bank numbers range from 0 to 7, where bank 7 is a no operation (“NOP”) bank, meaning data will be discarded on a “write” and zero filled on a “read”.
- NOP no operation
- the stride field provides an increment for addresses in on-board memory. The address is incremented by the stride value after all banks in the sequence are addressed.
- the gather/scatter indexes are 32-bit/4-byte quantities taken from on-board memory. Each index is added, sign-extended, to the address base in DRcc, after having been multiplied/shifted by the operand size.
- the address in register DRaa is a byte address.
- DRaa At least the bottom 50 bits of the address specifier must be valid.
- DRcc the number of address bits that must be valid is implementation dependent.
- All common memory addresses are virtual and are translated using translation look-aside buffers loaded from a MAP's status and control page.
- On-board memory addresses are physical and are not modified or translated.
- the direct memory access command sets or clears a flag register when the last specified data has been moved. For writes, this is done when the last data has been read from on-board memory and is on its way to common memory 50 ( FIG. 2 ). For reads, this is done when the last data has been written to on-board memory 50 ( FIG. 2 ).
- This command does not support waiting on a flag register value. If this is necessary, a DMA Flag Set command with the parameter fields set to wait for the needed value is available.
- DMA functions be issued as quickly as is reasonably possible for an implementation and with maximum parallelism. One operation does not have to complete before another is started unless wait commands are placed between operations, allowing multiple DMA operations to be processing simultaneously.
- the DMA Flag Set Command sets Flag register bits. It can do this when the DMA Flag Set command becomes available for issue or the command can wait for some DMA activity to be completed. This allows synchronization of the data movement of the DMA with the execution of a flag command. This command can also be followed with U_Data commands if it is desired to transfer command or data parameters to the user array after a DMA operation is complete.
- the DMA Flag Set Command is a two word command.
- the first word contains the command data and the second word contains immediate values for the flag register (i.e. bit 2 is applied to FR 2 , bit 3 to FR 3 . . . , bit 31 to FR 31 ).
- Any flag register that corresponds to a 1 bit in the mm field is set to a 1. Any flag register that corresponds to a 0 bit is not changed.
- the command lets the completion of a DMA action set any of the selected flag registers.
- Register-to-Register Data Register Arithmetic/Logic Commands do register-to-register integer add and subtract operations, and OR, AND, and XOR bitwise logical operations.
- DRcc is the minuend and DRdd is the subtrahend.
- Arithmetic operations are as follows: DRee ⁇ DRcc ⁇ DRdd.
- Bitwise logical operations are as follows: DRee ⁇ DRcc OR/AND/XOR DRdd. Overflow is not detected.
- Immediate Data Register Arithmetic/Logic Commands add, subtract, OR, AND, or XOR 64-bit immediate values to Data Registers.
- the Immediate Data Register Arithmetic/Logic Command is a two-word command. The first word contains the command data and the second word contains the 64-bit immediate value.
- Single Data Register Load/Store Commands allow for a single Data register to be loaded from or stored to on-board memory. All 8 bytes are moved.
- DRee The contents of DRee are loaded or stored according to the a parameter.
- the on-board memory address referred to is DRcc+DRdd. Overflow is not detected.
- Multiple Data Register Load/Store Commands are two-word commands using 32-bit immediate values.
- the first word contains the command data and the second word contains immediate values for the data registers (i.e. bit 2 is applied to DR 2 , bit 3 to DR 3 . . . , bit 31 to DR 31 ).
- Any of the data registers can be moved to/from on-board memory.
- Each 1 bit in the immediate value enables the corresponding data register to be loaded or stored.
- Each Data register that has a corresponding 0 bit is ignored.
- the data in on-board memory is packed/compressed. (For example, if the immediate value has only two 1 bits corresponding to DR 3 and DR 10 and the on-board memory address is 1000 in a store operation, then DR 3 is stored in on-board memory in word 1000 and DR 10 is stored in 1001.)
- Data Register Branch Command tests a data register for a zero/nonzero state. If the test is successful, a branch to the specified command in the ComList is taken; otherwise the next command in the ComList is executed.
- Valid command addresses would be 1 through 495 providing that it is a command word and not an immediate data address. All bits in hh must be valid otherwise execution is undefined.
- Register-to-Register Flag Register Logic Commands perform logic operations on the Flag registers.
- FR 0 is always 0/clear, and FR 1 is always a 1/set. If FR 31 sets, and interrupts are enabled, an interrupt and halt is generated after control logic idles down command execution and stores status to the MAP's status and control area. If FR 31 is set when a command attempts to set it again, no further or secondary interrupt is generated from the attempt to set the Flag, but the interrupt Cause Bits are saved in MAP status. Setting FR 31 will always halt MAP execution.
- Immediate Flag Register Logic commands perform logic operations on all 32 Flag registers at the same time. Each bit of the immediate value in the command is logically combined with the respective Flag Register with results written back to each register bit. Bits 0 and 1 of the immediate value (bits 32 and 33 of the command) are ignored as FR 1 and FR 1 are constant values. This command is similar to a DMA Flag Set command with the exception that the DMA wait bits are set to 0.
- Flag Register Branch A FR is tested for zero/nonzero. If the test is successful branch to the specified command in ComList, otherwise execute the next command in the list.
- Valid command addresses would be 1 through 495 providing that it is a command word and not an immediate data address. All bits in hh must be valid; otherwise execution is undefined.
- DR Data U_Data Command sends command and parameter information from a specified data register to the user array. It is up to the logic that receives the data to interpret it as needed. This command transfers data from the DR defined in field dd to the User_Register defined in field cc. There are up to 32 user registers that are contained in a section of RAM above where the Data Registers are located. The User Registers differ from the Data Registers in being unidirectional from the control logic to the user array. When the ComList has filled the desired number of User Registers, it should set the Last Transfer bit in field f indicating that this is the last User Register of the group to be transferred. A user register available signal is raised and is available to the user logic when field f is set to indicate tht the last user register is transferred.
- Immediate Data U_Data Command is a 16-byte command that sends command and parameter information from an immediate value in the command to the user array. It is up to the logic that receives the data to interpret it as needed. This command transfers immediate data to the User_Register defined in field cc. There are up to 32 User Registers that are contained in a section of RAM above where the Data Registers are located. The User Registers differ from the Data Registers in being unidirectional from the control logic to the user array. When the ComList has filled the desired number of User Registers, it should set the Last Transfer bit in field f to indicate this is the last User Register of the group transferred. A user register available signal is raised and is available to the user logic when field f is set to indicate tht the last user register is transferred.
- U_Data commands/parameters can be sent after the execution of the command DMA Flag Set. Up to thirty-two 64-bit immediate values can be sent from either Data Registers or the second immediate data words. It is up to the receiving user array to read and interpret the information sent. In turn, the user array can send Flag information back to the Flag Registers. Flag information can be returned without having been solicited by other commands. Thus, the user array can indicate that an internal user array action is complete and that it is time to start an external action, such as starting a DMA sequence to store a result. The user array can also request an interrupt by setting FR 31 . An interrupt request from the user array is processed the same as if the interrupt came from any other source (data error, ComList command, Illegal instruction, etc.).
- DMA activity can also interact with the user array.
- the DMA Flag Set command can be followed with U_Data commands. With multiple ways to control the Flag Registers and given that all commands can test the Flag Registers, coordinated interaction is easily done between all three elements of MAP: user array, DMA and other ComList processing.
- Fetch Configuration Data Command requests that the DMA move an FPGA configuration block of data between common memory and the MAP.
- the Fetch Configuration Data Command must be the last command in a ComList.
- One word command code 1001 DMA Configuration Data Command Code a, b unused c 0, clear Flag when data movement complete 1, set Flag when data movement complete d, e, f unused aa Common Memory address DR bb Movement complete FR cc User FPGA to configure (0, 1, 2, or 3) dd Data length DR (number of operands to be moved) ee, ff, gg, hh unused
- the command processor and the DMA will go into a special non-interruptible mode until the FPGA is configured.
- configuration normal ComList commands will not be fetched or executed from the ComList area of common memory.
- the user FPGAs are checked for proper configuration. When the FPGA has been properly configured, a status indication and interrupt will be returned to the processor indicating that the MAP is returning to normal operation.
- Direct Commands are sent directly to a MAP from an instruction processor or another MAP, therefore they are not included in a ComList. These commands give a real-time and direct control to meet operating system needs, and driver requirements. Direct commands have no parameters.
- Stopping/halting MAP execution can result from several sources. In all cases this requires setting or attempting to set FR 31 . When there is an attempt to set FR 31 either directly, as with the ComList DMA Flag Set command, or indirectly, as with the direct Stop command, or as a result of some internal error, execution of the MAP is halted.
- Stop Upon any halt or exception, with Stop enabled, the following occurs:
- MAP control logic comes to the most graceful halt it can, waiting for execution logic to go quiet.
- Control state is saved in on-board memory addresses 0–31. This state includes everything needed to continue execution, for example from a TLB/Page Table miss. This area in on-board memory is reserved for this use.
- the MAP's TLB registers are stored into the TLB area of its Base page.
- Stop is not enabled, the sequence above is executed except that in the last step the command that caused the error is abandoned and execution continues.
- Status consists of several registers as listed below.
- the 8-byte Index column shows the address offset from the start of a MAP's status and control area as an 8-byte word index.
- Bit Parameters 0 1, and 2 are the zero-values.
- the Interrupt ID parameter need not be valid if interrupts are disabled. Page Table Base must be valid and point to an end-of-table entry.
Abstract
Description
bit | 63 | 00 | ||||||||||||||
field | size | code | a | b | c | d | e | f | aa | bb | cc | dd | ee | ff | gg | |
width | ||||||||||||||||
2 | 4 | 1 | 1 | 1 | 1 | 1 | 1 | 5 | 5 | 5 | 5 | 5 | 5 | 12 | 10 | |
size | 00, One word command |
code | 000, ComList Length Command Code |
a, b, c, d, e, |
0, unused |
aa, bb, cc, dd, ee, ff, |
0, unused |
hh | ComList length (2 to 496) |
size | 00, One word command |
code | 0000, DMA Command Code |
a | 0, Load (move data to on-board memory from common |
memory) | |
1, Store (move data to common memory from on-board | |
memory) | |
|
0, |
1, Gather from on-board memory (if a = 1), Scatter to on- | |
board memory (if a = 0) | |
|
0, clear Flag when data movement complete |
1, set Flag when data movement complete | |
d, e, f | unused |
aa | Common memory address data register (“DR”) |
bb | Movement complete flag register (“FR”) |
cc | On-board memory address DR |
dd | Data length DR (number of operands to be moved) |
ee | Stride DR (if b = 0), |
Gather/Scatter address in on-board memory DR (if b = 1) | |
ff, gg, hh | unused |
BIT | 63:60 | 59:52 | 51:04 | 03:00 |
FIELD | UNUSED | STRIDE | BANK SEQUENCE | MODULUS |
WIDTH | 4 | 8 | 16 | 4 |
3 BIT FIELDS | ||||
size | 01, Two-word command |
code | 0100, DMA Flag Set Command Code |
a | 0, don't wait for DMA read |
1, wait for DMA read | |
b | |
0, don't wait for |
|
1, wait for DMA write | |
c | |
0, | |
d | |
0, wait until flag clear | |
1, wait until flag set | |
e, f | unused |
aa | Operation (numbers are base 16) |
11, Or | |
bb | Wait Flag FR |
cc, dd, ee, ff, gg, hh | |
mm | |
64 bit immediate value (bit2 is applied to FR2, | |
bit3 to FR3 . . . , bit 31 to FR31 | |
size | 00, One word command | ||
code | 0001, DR arithmetic | ||
a, b, c, | | ||
d | |||
0, wait until flag clear | |||
1, wait until flag set | |||
e, f | unused | ||
aa | Operation (numbers are base 16) | ||
00, Add | |||
01, Sub | |||
03, OR | |||
04, AND | |||
05, XOR | |||
bb | Wait Flag FR | ||
cc | Source1 DR | ||
dd | Source2 DR | ||
ee | Result DR | ||
ff, gg, hh | unused | ||
size | 01, Two word command | ||
code | 0001, DR arithmetic | ||
a, b, c, | | ||
d | |||
0, wait until flag clear | |||
1, wait until flag set | |||
e, f | unused | ||
aa | Operation (numbers are base 16) | ||
00, Add | |||
01, Sub | |||
03, OR | |||
04, AND | |||
05, XOR | |||
bb | Wait Flag | ||
cc | Source | ||
1 | |||
dd | |||
0, unused | |||
ee | Result DR | ||
ff, gg, hh | | ||
mm | |||
64 bit immediate value | |||
The addition and subtraction operations are as follows: DRee←DRcc±(mm). The logical operations are as follows: Dree←DRcc OR/AND/XOR (mm). Overflow is not detected.
size | 00, One word command | ||
code | 0010, DR Load/Store | ||
a | 0, Load (move data to DRs from On-board memory) | ||
1, Store (move data to On-board memory from DRs) | |||
b, c | | ||
d | |||
0, wait until flag clear | |||
1, wait until flag set | |||
aa | unused | ||
bb | Wait Flag FR | ||
cc | Address base DR | ||
dd | Address index DR | ||
ee | DR to Load (a = 0) or Store (a = 1) | ||
ff, gg, hh | unused | ||
size | 01, Two word command |
code | 0010, DR Load/Store |
a | 0, Load (move data to DRs from On-board memory) |
1, Store (move data to On-board memory from DRs) | |
b, c | unused |
e, f | |
d | |
0, wait until flag clear | |
1, wait until flag set | |
aa | unused |
bb | Wait Flag FR |
cc | On-board memory address DR |
dd, ee, ff, gg, hh | |
mm | |
64 bit immediate value | |
size | 00, One word command | ||
code | 0011, DR Branch | ||
a | | ||
b | |||
0, test (cc) for zero | |||
1, test (cc) for | |||
c | |||
0, | |||
d | |||
0, wait until flag clear | |||
1, wait until flag set | |||
aa | unused | ||
bb | Wait flag FR | ||
cc | Tested DR | ||
dd, ee, ff, gg | unused | ||
hh | Branch index immediate | ||
size | 00, One word command | ||
code | 0100, FR Logic | ||
a, b, c, | | ||
d | |||
0, wait until flag clear | |||
1, wait until flag set | |||
e, f | unused | ||
aa | Operation (numbers are base 16) | ||
10, AND | |||
11, OR | |||
12, XOR | |||
bb | Wait Flag | ||
cc | Source | ||
1 | |||
dd | Source | ||
2 FR | |||
ee | Result FR | ||
ff, gg, hh | unused | ||
size | 01, Two word command |
code | 0100, FR Logic |
a | 0, |
b | |
0, | |
c | |
0, | |
d | |
0, wait until flag clear | |
1, wait until flag set | |
e, f | unused |
aa | Operation (numbers are base 16) |
10, AND | |
11, OR | |
12, XOR | |
bb | Wait Flag FR |
cc, dd, ee, ff, gg, hh | |
mm | |
64 bit immediate value (bit2 is applied to FR2, | |
bit3 to FR3 . . . , bit31 to FR31) | |
size | 00, One word command | ||
code | 0101, FR Branch | ||
a | | ||
b | |||
0, test (cc) for zero | |||
1, test (cc) for | |||
c | |||
0, | |||
d | |||
0, wait until flag clear | |||
1, wait until flag set | |||
aa | unused | ||
bb | Wait flag FR | ||
cc | Tested FR | ||
dd, ee, ff, gg | unused | ||
hh | Branch index immediate | ||
size | 00, One-word command | ||
code | 0110 U_Logic Command Code | ||
a, b, |
0, | ||
d | |||
0, wait until FR wait flag clear | |||
1, wait until FR wait flag set | |||
|
0, | ||
f | |||
0, more U_Data coming | |||
1, last U_Data transfer | |||
aa | unused | ||
bb | Wait Flag FR | ||
cc | U_Data register address (0 through 31) | ||
dd | DR Register for U_Data source | ||
ee, ff, gg, hb | unused | ||
size | 01, Two-word command | ||
code | 0110, U_Logic Command Code | ||
a, b, |
0, | ||
d | |||
0, wait until FR wait flag clear | |||
1, wait until FR wait flag set | |||
|
0, | ||
f | |||
0, more U_Data coming | |||
1, last U_Data transfer | |||
aa | unused | ||
bb | Wait Flag FR | ||
cc | U_Data register address (0 through 31) | ||
dd, ee, ff, gg, hh | | ||
mm | |||
64 bit immediate value | |||
size | 00, One word command |
code | 1001, DMA Configuration Data Command Code |
a, b | |
c | |
0, clear Flag when data movement complete | |
1, set Flag when data movement complete | |
d, e, f | unused |
aa | Common Memory address DR |
bb | Movement complete FR |
cc | User FPGA to configure (0, 1, 2, or 3) |
dd | Data length DR (number of operands to be moved) |
ee, ff, gg, hh | unused |
Command | Function |
Initialize | Master Clear. |
Load Fixed Configuration | Configure the fixed portion of MAP |
logic from local MAP ROM. | |
Load Parameter Set | Get control parameters from Status |
and Control Area. | |
Stop | Finish any current instructions and |
halt. Save status in Status and | |
Control Area. | |
Fetch0 | Fetch ComList0 from common |
memory and begin execution. | |
Fetch1 | Fetch ComList1 from common |
memory and begin execution. | |
Continue | Fetch the next ComList entry and |
start execution. | |
Continue From Saved | Load state data from saved area in |
on-board memory and continue. | |
8-Byte | ||||
Index | Field | | Function | |
0 | Stopped | 00 | 1 if MAP is stopped |
| 1–8 | ||
Missed | 1 | Requested page not | |
ComList | |||
2 | Executed Halt command | ||
Illegal | 3 | Illegal instruction | |
in ComList | |||
U_Logic Interrupt | 4 | U_Logic interrupt | |
(set FR31) | |||
ComList Interrupt | 5 | ComList command | |
(set FR31) | |||
DMA Data | 6 | DMA Data error | |
(affected by Stop | |||
on Corr_Err) | |||
U_Data | 7 | U_Logic determined data | |
error | |||
Other Data | 8 | Other MAP data error | |
ComList Pointer | 32–41 | | |
2 | Miss Address | 00–49 | Virtual address that caused |
page miss | |||
4 | Data Address | 00–51 | Common Memory address |
of DMA | |||
Syndrome | |||
52–63 | Syndrome of data error | ||
5 | Data | 00–63 | Data word in error |
Positions not shown in the table are stored as 0 bits. Bit3/Illegal is also set, and execution halted, if the last command in the ComList page is executed and is not a taken branch.
8-Byte | |||
Index | Field | Bit Position | Function |
8 | Bit Parameters | 00–07 | Cell text |
Disable interrupts | 0 | 0-Interrupts enabled | |
1-Interrupts disabled | |||
Contu on |
1 | 0-Stop execution on error | |
1-Continue command | |||
execution on error | |||
Stop on Corr- |
2 | 0-Continue execution if | |
corrected error | |||
1-Halt execution if | |||
corrected | |||
Maintenance | |||
1 | 6 | ||
|
7 | ||
Interrupt ID | 32–41 | ID number of processor to | |
interrupt | |||
10 | Page Table Base | 00–39 | Physical address of |
Page Table | |||
Claims (10)
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/011,835 US7155602B2 (en) | 2001-04-30 | 2001-12-05 | Interface for integrating reconfigurable processors into a general purpose computing system |
AU2002254549A AU2002254549A1 (en) | 2001-12-05 | 2002-04-05 | An interface for integrating reconfigurable processors into a general purpose computing system |
EP02723783A EP1459219A4 (en) | 2001-12-05 | 2002-04-05 | An interface for integrating reconfigurable processors into a general purpose computing system |
PCT/US2002/010813 WO2003050723A1 (en) | 2001-12-05 | 2002-04-05 | An interface for integrating reconfigurable processors into a general purpose computing system |
US11/140,718 US7167976B2 (en) | 2001-04-30 | 2005-05-31 | Interface for integrating reconfigurable processors into a general purpose computing system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US28697901P | 2001-04-30 | 2001-04-30 | |
US10/011,835 US7155602B2 (en) | 2001-04-30 | 2001-12-05 | Interface for integrating reconfigurable processors into a general purpose computing system |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/140,718 Continuation US7167976B2 (en) | 2001-04-30 | 2005-05-31 | Interface for integrating reconfigurable processors into a general purpose computing system |
Publications (2)
Publication Number | Publication Date |
---|---|
US20030046530A1 US20030046530A1 (en) | 2003-03-06 |
US7155602B2 true US7155602B2 (en) | 2006-12-26 |
Family
ID=26682844
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/011,835 Active 2024-05-04 US7155602B2 (en) | 2001-04-30 | 2001-12-05 | Interface for integrating reconfigurable processors into a general purpose computing system |
US11/140,718 Expired - Lifetime US7167976B2 (en) | 2001-04-30 | 2005-05-31 | Interface for integrating reconfigurable processors into a general purpose computing system |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/140,718 Expired - Lifetime US7167976B2 (en) | 2001-04-30 | 2005-05-31 | Interface for integrating reconfigurable processors into a general purpose computing system |
Country Status (1)
Country | Link |
---|---|
US (2) | US7155602B2 (en) |
Cited By (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050097535A1 (en) * | 2003-09-15 | 2005-05-05 | Plum Thomas S. | Automated safe secure techniques for eliminating undefined behavior in computer software |
US20050246693A1 (en) * | 2003-09-15 | 2005-11-03 | Plum Thomas S | Automated safe secure techniques for eliminating undefined behavior in computer software |
US20060130021A1 (en) * | 2003-09-15 | 2006-06-15 | Plum Thomas S | Automated safe secure techniques for eliminating undefined behavior in computer software |
US20070192576A1 (en) * | 2006-02-16 | 2007-08-16 | Moore Charles H | Circular register arrays of a computer |
US20070192566A1 (en) * | 2006-02-16 | 2007-08-16 | Moore Charles H | Method and apparatus for monitoring inputs to a computer |
US20080270648A1 (en) * | 2007-04-27 | 2008-10-30 | Technology Properties Limited | System and method for multi-port read and write operations |
US7818729B1 (en) | 2003-09-15 | 2010-10-19 | Thomas Plum | Automated safe secure techniques for eliminating undefined behavior in computer software |
US20100309511A1 (en) * | 2009-06-04 | 2010-12-09 | Canon Kabushiki Kaisha | Image processing apparatus and control method thereof, computer-readable storage medium |
US7904615B2 (en) | 2006-02-16 | 2011-03-08 | Vns Portfolio Llc | Asynchronous computer communication |
US7937557B2 (en) | 2004-03-16 | 2011-05-03 | Vns Portfolio Llc | System and method for intercommunication between computers in an array |
US7966481B2 (en) | 2006-02-16 | 2011-06-21 | Vns Portfolio Llc | Computer system and method for executing port communications without interrupting the receiving computer |
US20110185152A1 (en) * | 2010-01-27 | 2011-07-28 | Fujitsu Semiconductor Limited | Reconfigurable circuit and semiconductor integrated circuit |
EP2605105A2 (en) | 2011-12-16 | 2013-06-19 | SRC Computers, LLC | Mobile electronic devices utilizing reconfigurable processing techniques to enable higher speed applications with lowered power consumption |
US8869123B2 (en) | 2011-06-24 | 2014-10-21 | Robert Keith Mykland | System and method for applying a sequence of operations code to program configurable logic circuitry |
EP2808802A2 (en) | 2013-05-28 | 2014-12-03 | SRC Computers, LLC | Multi-processor computer architecture incorporating distributed multi-ported common memory modules |
US9153311B1 (en) | 2014-05-27 | 2015-10-06 | SRC Computers, LLC | System and method for retaining DRAM data when reprogramming reconfigurable devices with DRAM memory controllers |
US9158544B2 (en) | 2011-06-24 | 2015-10-13 | Robert Keith Mykland | System and method for performing a branch object conversion to program configurable logic circuitry |
US9304770B2 (en) | 2011-11-21 | 2016-04-05 | Robert Keith Mykland | Method and system adapted for converting software constructs into resources for implementation by a dynamically reconfigurable processor |
US9411613B1 (en) | 2015-04-22 | 2016-08-09 | Ryft Systems, Inc. | Systems and methods for managing execution of specialized processors |
US9411528B1 (en) | 2015-04-22 | 2016-08-09 | Ryft Systems, Inc. | Storage management systems and methods |
US9530483B2 (en) | 2014-05-27 | 2016-12-27 | Src Labs, Llc | System and method for retaining dram data when reprogramming reconfigurable devices with DRAM memory controllers incorporating a data maintenance block colocated with a memory module or subsystem |
US9542244B2 (en) | 2015-04-22 | 2017-01-10 | Ryft Systems, Inc. | Systems and methods for performing primitive tasks using specialized processors |
US9633160B2 (en) | 2012-06-11 | 2017-04-25 | Robert Keith Mykland | Method of placement and routing in a reconfiguration of a dynamically reconfigurable processor |
US10089277B2 (en) | 2011-06-24 | 2018-10-02 | Robert Keith Mykland | Configurable circuit array |
US11500644B2 (en) * | 2020-05-15 | 2022-11-15 | Alibaba Group Holding Limited | Custom instruction implemented finite state machine engines for extensible processors |
Families Citing this family (49)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10081643D2 (en) | 1999-06-10 | 2002-05-29 | Pact Inf Tech Gmbh | Sequence partitioning on cell structures |
US8058899B2 (en) | 2000-10-06 | 2011-11-15 | Martin Vorbach | Logic cell array and bus system |
US9411532B2 (en) | 2001-09-07 | 2016-08-09 | Pact Xpp Technologies Ag | Methods and systems for transferring data between a processing device and external devices |
US9141390B2 (en) | 2001-03-05 | 2015-09-22 | Pact Xpp Technologies Ag | Method of processing data with an array of data processors according to application ID |
US9250908B2 (en) | 2001-03-05 | 2016-02-02 | Pact Xpp Technologies Ag | Multi-processor bus and cache interconnection system |
US9552047B2 (en) | 2001-03-05 | 2017-01-24 | Pact Xpp Technologies Ag | Multiprocessor having runtime adjustable clock and clock dependent power supply |
US9436631B2 (en) | 2001-03-05 | 2016-09-06 | Pact Xpp Technologies Ag | Chip including memory element storing higher level memory data on a page by page basis |
US7840777B2 (en) * | 2001-05-04 | 2010-11-23 | Ascenium Corporation | Method and apparatus for directing a computational array to execute a plurality of successive computational array instructions at runtime |
US10031733B2 (en) | 2001-06-20 | 2018-07-24 | Scientia Sol Mentis Ag | Method for processing data |
US6836823B2 (en) * | 2001-11-05 | 2004-12-28 | Src Computers, Inc. | Bandwidth enhancement for uncached devices |
US20140143509A1 (en) * | 2002-03-21 | 2014-05-22 | Pact Xpp Technologies Ag | Method and device for data processing |
US9170812B2 (en) | 2002-03-21 | 2015-10-27 | Pact Xpp Technologies Ag | Data processing system having integrated pipelined array data processor |
AU2003289844A1 (en) | 2002-09-06 | 2004-05-13 | Pact Xpp Technologies Ag | Reconfigurable sequencer structure |
US7149867B2 (en) * | 2003-06-18 | 2006-12-12 | Src Computers, Inc. | System and method of enhancing efficiency and utilization of memory bandwidth in reconfigurable hardware |
JP2005092742A (en) * | 2003-09-19 | 2005-04-07 | Toshiba Corp | Video output controller and video card |
US7599299B2 (en) * | 2004-04-30 | 2009-10-06 | Xilinx, Inc. | Dynamic reconfiguration of a system monitor (DRPORT) |
JP2006338538A (en) * | 2005-06-03 | 2006-12-14 | Nec Electronics Corp | Stream processor |
US7716100B2 (en) * | 2005-12-02 | 2010-05-11 | Kuberre Systems, Inc. | Methods and systems for computing platform |
KR100812346B1 (en) * | 2006-02-06 | 2008-03-11 | 삼성전자주식회사 | Method and Apparatus for Interrupt Handling in Reconfigurable Array |
WO2008004158A1 (en) * | 2006-07-03 | 2008-01-10 | Nxp B.V. | Method and system for configuration of a hardware peripheral |
US8639852B2 (en) * | 2009-11-13 | 2014-01-28 | Qualcomm Incorporated | Burst access protocol |
WO2011060313A1 (en) * | 2009-11-13 | 2011-05-19 | Qualcomm Incorporated | Burst access protocol and priority initialization of a second processor |
US8645663B2 (en) | 2011-09-12 | 2014-02-04 | Mellanox Technologies Ltd. | Network interface controller with flexible memory handling |
US9721319B2 (en) * | 2011-10-14 | 2017-08-01 | Mastercard International Incorporated | Tap and wireless payment methods and devices |
US9143467B2 (en) | 2011-10-25 | 2015-09-22 | Mellanox Technologies Ltd. | Network interface controller with circular receive buffer |
US8751701B2 (en) | 2011-12-26 | 2014-06-10 | Mellanox Technologies Ltd. | Host channel adapter with pattern-type DMA |
US9256545B2 (en) | 2012-05-15 | 2016-02-09 | Mellanox Technologies Ltd. | Shared memory access using independent memory maps |
US8767009B1 (en) * | 2012-06-26 | 2014-07-01 | Google Inc. | Method and system for record-time clipping optimization in display list structure |
US8761189B2 (en) | 2012-06-28 | 2014-06-24 | Mellanox Technologies Ltd. | Responding to dynamically-connected transport requests |
US8914458B2 (en) | 2012-09-27 | 2014-12-16 | Mellanox Technologies Ltd. | Look-ahead handling of page faults in I/O operations |
US9639464B2 (en) | 2012-09-27 | 2017-05-02 | Mellanox Technologies, Ltd. | Application-assisted handling of page faults in I/O operations |
US8745276B2 (en) | 2012-09-27 | 2014-06-03 | Mellanox Technologies Ltd. | Use of free pages in handling of page faults |
US9298642B2 (en) | 2012-11-01 | 2016-03-29 | Mellanox Technologies Ltd. | Sharing address translation between CPU and peripheral devices |
US9727503B2 (en) | 2014-03-17 | 2017-08-08 | Mellanox Technologies, Ltd. | Storage system and server |
US9696942B2 (en) | 2014-03-17 | 2017-07-04 | Mellanox Technologies, Ltd. | Accessing remote storage devices using a local bus protocol |
US10031857B2 (en) | 2014-05-27 | 2018-07-24 | Mellanox Technologies, Ltd. | Address translation services for direct accessing of local memory over a network fabric |
US10120832B2 (en) | 2014-05-27 | 2018-11-06 | Mellanox Technologies, Ltd. | Direct access to local memory in a PCI-E device |
CN108292279A (en) * | 2015-08-24 | 2018-07-17 | Src实验室有限责任公司 | When with reprograming reconfigurable device comprising the DRAM storage controls with memory module or the juxtaposed data dimension protecting block of subsystem, retain the system and method for DRAM data |
US10148581B2 (en) | 2016-05-30 | 2018-12-04 | Mellanox Technologies, Ltd. | End-to-end enhanced reliable datagram transport |
US10516710B2 (en) | 2017-02-12 | 2019-12-24 | Mellanox Technologies, Ltd. | Direct packet placement |
US10210125B2 (en) | 2017-03-16 | 2019-02-19 | Mellanox Technologies, Ltd. | Receive queue with stride-based data scattering |
US11252464B2 (en) | 2017-06-14 | 2022-02-15 | Mellanox Technologies, Ltd. | Regrouping of video data in host memory |
US10367750B2 (en) | 2017-06-15 | 2019-07-30 | Mellanox Technologies, Ltd. | Transmission and reception of raw video using scalable frame rate |
US10474600B2 (en) | 2017-09-14 | 2019-11-12 | Samsung Electronics Co., Ltd. | Heterogeneous accelerator for highly efficient learning systems |
RU2713757C1 (en) * | 2019-04-29 | 2020-02-07 | Федеральное государственное унитарное предприятие "Научно-исследовательский институт "Квант" | Reconfigurable computing system |
US11940933B2 (en) | 2021-03-02 | 2024-03-26 | Mellanox Technologies, Ltd. | Cross address-space bridging |
US11934333B2 (en) | 2021-03-25 | 2024-03-19 | Mellanox Technologies, Ltd. | Storage protocol emulation in a peripheral device |
US11934658B2 (en) | 2021-03-25 | 2024-03-19 | Mellanox Technologies, Ltd. | Enhanced storage protocol emulation in a peripheral device |
US11726666B2 (en) | 2021-07-11 | 2023-08-15 | Mellanox Technologies, Ltd. | Network adapter with efficient storage-protocol emulation |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4916692A (en) | 1988-03-14 | 1990-04-10 | Racal Data Communications Inc. | TDM bus controller |
US5036473A (en) | 1988-10-05 | 1991-07-30 | Mentor Graphics Corporation | Method of using electronically reconfigurable logic circuits |
US5329630A (en) | 1988-03-23 | 1994-07-12 | Dupont Pixel Systems Limited | System and method using double-buffer preview mode |
US5448496A (en) | 1988-10-05 | 1995-09-05 | Quickturn Design Systems, Inc. | Partial crossbar interconnect architecture for reconfigurably connecting multiple reprogrammable logic devices in a logic emulation system |
US5664195A (en) * | 1993-04-07 | 1997-09-02 | Sequoia Systems, Inc. | Method and apparatus for dynamic installation of a driver on a computer system |
US6052773A (en) * | 1995-02-10 | 2000-04-18 | Massachusetts Institute Of Technology | DPGA-coupled microprocessors |
US6434687B1 (en) * | 1997-12-17 | 2002-08-13 | Src Computers, Inc. | System and method for accelerating web site access and processing utilizing a computer system incorporating reconfigurable processors operating under a single operating system image |
US6438737B1 (en) * | 2000-02-15 | 2002-08-20 | Intel Corporation | Reconfigurable logic for a computer |
US6542998B1 (en) * | 1997-02-08 | 2003-04-01 | Pact Gmbh | Method of self-synchronization of configurable elements of a programmable module |
US6564179B1 (en) * | 1999-07-26 | 2003-05-13 | Agere Systems Inc. | DSP emulating a microcontroller |
US6753925B2 (en) * | 2001-03-30 | 2004-06-22 | Tektronix, Inc. | Audio/video processing engine |
US6825698B2 (en) * | 2001-08-29 | 2004-11-30 | Altera Corporation | Programmable high speed I/O interface |
US6859869B1 (en) * | 1995-11-17 | 2005-02-22 | Pact Xpp Technologies Ag | Data processing system |
US6964029B2 (en) * | 2002-10-31 | 2005-11-08 | Src Computers, Inc. | System and method for partitioning control-dataflow graph representations |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5708830A (en) * | 1992-09-15 | 1998-01-13 | Morphometrix Inc. | Asynchronous data coprocessor utilizing systolic array processors and an auxiliary microprocessor interacting therewith |
US6134605A (en) * | 1998-04-15 | 2000-10-17 | Diamond Multimedia Systems, Inc. | Redefinable signal processing subsystem |
EP1061439A1 (en) | 1999-06-15 | 2000-12-20 | Hewlett-Packard Company | Memory and instructions in computer architecture containing processor and coprocessor |
-
2001
- 2001-12-05 US US10/011,835 patent/US7155602B2/en active Active
-
2005
- 2005-05-31 US US11/140,718 patent/US7167976B2/en not_active Expired - Lifetime
Patent Citations (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4916692A (en) | 1988-03-14 | 1990-04-10 | Racal Data Communications Inc. | TDM bus controller |
US5329630A (en) | 1988-03-23 | 1994-07-12 | Dupont Pixel Systems Limited | System and method using double-buffer preview mode |
US5796623A (en) | 1988-10-05 | 1998-08-18 | Quickturn Design Systems, Inc. | Apparatus and method for performing computations with electrically reconfigurable logic devices |
US5812414A (en) | 1988-10-05 | 1998-09-22 | Quickturn Design Systems, Inc. | Method for performing simulation using a hardware logic emulation system |
US5452231A (en) | 1988-10-05 | 1995-09-19 | Quickturn Design Systems, Inc. | Hierarchically connected reconfigurable logic assembly |
US5612891A (en) | 1988-10-05 | 1997-03-18 | Quickturn Design Systems, Inc. | Hardware logic emulation system with memory capability |
US5657241A (en) | 1988-10-05 | 1997-08-12 | Quickturn Design Systems, Inc. | Routing methods for use in a logic emulation system |
US5661662A (en) | 1988-10-05 | 1997-08-26 | Quickturn Design Systems, Inc. | Structures and methods for adding stimulus and response functions to a circuit design undergoing emulation |
US6002861A (en) | 1988-10-05 | 1999-12-14 | Quickturn Design Systems, Inc. | Method for performing simulation using a hardware emulation system |
US5734581A (en) | 1988-10-05 | 1998-03-31 | Quickturn Design Systems, Inc. | Method for implementing tri-state nets in a logic emulation system |
US5036473A (en) | 1988-10-05 | 1991-07-30 | Mentor Graphics Corporation | Method of using electronically reconfigurable logic circuits |
US5448496A (en) | 1988-10-05 | 1995-09-05 | Quickturn Design Systems, Inc. | Partial crossbar interconnect architecture for reconfigurably connecting multiple reprogrammable logic devices in a logic emulation system |
US5664195A (en) * | 1993-04-07 | 1997-09-02 | Sequoia Systems, Inc. | Method and apparatus for dynamic installation of a driver on a computer system |
US6052773A (en) * | 1995-02-10 | 2000-04-18 | Massachusetts Institute Of Technology | DPGA-coupled microprocessors |
US6859869B1 (en) * | 1995-11-17 | 2005-02-22 | Pact Xpp Technologies Ag | Data processing system |
US6542998B1 (en) * | 1997-02-08 | 2003-04-01 | Pact Gmbh | Method of self-synchronization of configurable elements of a programmable module |
US6434687B1 (en) * | 1997-12-17 | 2002-08-13 | Src Computers, Inc. | System and method for accelerating web site access and processing utilizing a computer system incorporating reconfigurable processors operating under a single operating system image |
US6564179B1 (en) * | 1999-07-26 | 2003-05-13 | Agere Systems Inc. | DSP emulating a microcontroller |
US6438737B1 (en) * | 2000-02-15 | 2002-08-20 | Intel Corporation | Reconfigurable logic for a computer |
US6753925B2 (en) * | 2001-03-30 | 2004-06-22 | Tektronix, Inc. | Audio/video processing engine |
US6825698B2 (en) * | 2001-08-29 | 2004-11-30 | Altera Corporation | Programmable high speed I/O interface |
US6964029B2 (en) * | 2002-10-31 | 2005-11-08 | Src Computers, Inc. | System and method for partitioning control-dataflow graph representations |
Cited By (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050097535A1 (en) * | 2003-09-15 | 2005-05-05 | Plum Thomas S. | Automated safe secure techniques for eliminating undefined behavior in computer software |
US7810080B2 (en) | 2003-09-15 | 2010-10-05 | Thomas Plum | Automated safe secure techniques for eliminating undefined behavior in computer software |
US7856624B2 (en) | 2003-09-15 | 2010-12-21 | Thomas Plum | Automated safe secure techniques for eliminating undefined behavior in computer software |
US7584461B2 (en) * | 2003-09-15 | 2009-09-01 | Plum Thomas S | Automated safe secure techniques for eliminating undefined behavior in computer software |
US20050246693A1 (en) * | 2003-09-15 | 2005-11-03 | Plum Thomas S | Automated safe secure techniques for eliminating undefined behavior in computer software |
US20060130021A1 (en) * | 2003-09-15 | 2006-06-15 | Plum Thomas S | Automated safe secure techniques for eliminating undefined behavior in computer software |
US7818729B1 (en) | 2003-09-15 | 2010-10-19 | Thomas Plum | Automated safe secure techniques for eliminating undefined behavior in computer software |
US7937557B2 (en) | 2004-03-16 | 2011-05-03 | Vns Portfolio Llc | System and method for intercommunication between computers in an array |
US20070192566A1 (en) * | 2006-02-16 | 2007-08-16 | Moore Charles H | Method and apparatus for monitoring inputs to a computer |
US7934075B2 (en) * | 2006-02-16 | 2011-04-26 | Vns Portfolio Llc | Method and apparatus for monitoring inputs to an asyncrhonous, homogenous, reconfigurable computer array |
US7904615B2 (en) | 2006-02-16 | 2011-03-08 | Vns Portfolio Llc | Asynchronous computer communication |
US20070192576A1 (en) * | 2006-02-16 | 2007-08-16 | Moore Charles H | Circular register arrays of a computer |
US7966481B2 (en) | 2006-02-16 | 2011-06-21 | Vns Portfolio Llc | Computer system and method for executing port communications without interrupting the receiving computer |
US7617383B2 (en) | 2006-02-16 | 2009-11-10 | Vns Portfolio Llc | Circular register arrays of a computer |
US8825924B2 (en) | 2006-02-16 | 2014-09-02 | Array Portfolio Llc | Asynchronous computer communication |
US7555637B2 (en) | 2007-04-27 | 2009-06-30 | Vns Portfolio Llc | Multi-port read/write operations based on register bits set for indicating select ports and transfer directions |
US20080270648A1 (en) * | 2007-04-27 | 2008-10-30 | Technology Properties Limited | System and method for multi-port read and write operations |
US8477383B2 (en) * | 2009-06-04 | 2013-07-02 | Canon Kabushiki Kaisha | Processing based on command and register |
US20100309511A1 (en) * | 2009-06-04 | 2010-12-09 | Canon Kabushiki Kaisha | Image processing apparatus and control method thereof, computer-readable storage medium |
US20110185152A1 (en) * | 2010-01-27 | 2011-07-28 | Fujitsu Semiconductor Limited | Reconfigurable circuit and semiconductor integrated circuit |
US9720879B2 (en) * | 2010-01-27 | 2017-08-01 | Cypress Semiconductor Corporation | Reconfigurable circuit having rows of a matrix of registers connected to corresponding ports and a semiconductor integrated circuit |
US8869123B2 (en) | 2011-06-24 | 2014-10-21 | Robert Keith Mykland | System and method for applying a sequence of operations code to program configurable logic circuitry |
US10089277B2 (en) | 2011-06-24 | 2018-10-02 | Robert Keith Mykland | Configurable circuit array |
US9158544B2 (en) | 2011-06-24 | 2015-10-13 | Robert Keith Mykland | System and method for performing a branch object conversion to program configurable logic circuitry |
US9304770B2 (en) | 2011-11-21 | 2016-04-05 | Robert Keith Mykland | Method and system adapted for converting software constructs into resources for implementation by a dynamically reconfigurable processor |
EP2605105A2 (en) | 2011-12-16 | 2013-06-19 | SRC Computers, LLC | Mobile electronic devices utilizing reconfigurable processing techniques to enable higher speed applications with lowered power consumption |
US9633160B2 (en) | 2012-06-11 | 2017-04-25 | Robert Keith Mykland | Method of placement and routing in a reconfiguration of a dynamically reconfigurable processor |
EP2808802A2 (en) | 2013-05-28 | 2014-12-03 | SRC Computers, LLC | Multi-processor computer architecture incorporating distributed multi-ported common memory modules |
US10741226B2 (en) | 2013-05-28 | 2020-08-11 | Fg Src Llc | Multi-processor computer architecture incorporating distributed multi-ported common memory modules |
EP2950218A1 (en) | 2014-05-27 | 2015-12-02 | SRC Computers, LLC | System and method for retaining dram data when reprogramming reconfigurable devices with dram memory controllers |
US9530483B2 (en) | 2014-05-27 | 2016-12-27 | Src Labs, Llc | System and method for retaining dram data when reprogramming reconfigurable devices with DRAM memory controllers incorporating a data maintenance block colocated with a memory module or subsystem |
US9153311B1 (en) | 2014-05-27 | 2015-10-06 | SRC Computers, LLC | System and method for retaining DRAM data when reprogramming reconfigurable devices with DRAM memory controllers |
US9411613B1 (en) | 2015-04-22 | 2016-08-09 | Ryft Systems, Inc. | Systems and methods for managing execution of specialized processors |
US9411528B1 (en) | 2015-04-22 | 2016-08-09 | Ryft Systems, Inc. | Storage management systems and methods |
US9542244B2 (en) | 2015-04-22 | 2017-01-10 | Ryft Systems, Inc. | Systems and methods for performing primitive tasks using specialized processors |
US11500644B2 (en) * | 2020-05-15 | 2022-11-15 | Alibaba Group Holding Limited | Custom instruction implemented finite state machine engines for extensible processors |
Also Published As
Publication number | Publication date |
---|---|
US7167976B2 (en) | 2007-01-23 |
US20050223213A1 (en) | 2005-10-06 |
US20030046530A1 (en) | 2003-03-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7155602B2 (en) | Interface for integrating reconfigurable processors into a general purpose computing system | |
US4648034A (en) | Busy signal interface between master and slave processors in a computer system | |
US9009408B2 (en) | Non-blocking, pipelined write allocates with allocate data merging in a multi-level cache system | |
EP0557884B1 (en) | Data processor having a cache memory and method | |
US6594713B1 (en) | Hub interface unit and application unit interfaces for expanded direct memory access processor | |
US6779065B2 (en) | Mechanism for interrupt handling in computer systems that support concurrent execution of multiple threads | |
US20040193837A1 (en) | CPU datapaths and local memory that executes either vector or superscalar instructions | |
KR100981033B1 (en) | Method and apparatus for interfacing a processor to a coprocessor | |
EP1309918A1 (en) | System and method for semaphore and atomic operation management in a multiprocessor | |
JP4226085B2 (en) | Microprocessor and multiprocessor system | |
US6594711B1 (en) | Method and apparatus for operating one or more caches in conjunction with direct memory access controller | |
EP3901776A1 (en) | Remap address space controller | |
US9910801B2 (en) | Processor model using a single large linear registers, with new interfacing signals supporting FIFO-base I/O ports, and interrupt-driven burst transfers eliminating DMA, bridges, and external I/O bus | |
US9965395B2 (en) | Memory attribute sharing between differing cache levels of multilevel cache | |
US20170147345A1 (en) | Multiple operation interface to shared coprocessor | |
US20040177224A1 (en) | Local memory with ownership that is transferrable between neighboring processors | |
US20050182915A1 (en) | Chip multiprocessor for media applications | |
WO2003050723A1 (en) | An interface for integrating reconfigurable processors into a general purpose computing system | |
US11449336B2 (en) | Method of storing register data elements to interleave with data elements of a different register, a processor thereof, and a system thereof | |
JPH01243123A (en) | Information processing unit | |
JPH02219153A (en) | Memory, cpu, processor element, and processor unit |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SRC COMPUTER, INC., COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:POZNANOVIC, DANIEL;REEL/FRAME:012385/0068 Effective date: 20011205 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
REMI | Maintenance fee reminder mailed | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
SULP | Surcharge for late payment | ||
AS | Assignment |
Owner name: FREEMAN CAPITAL PARTNERS LP, TEXAS Free format text: SECURITY AGREEMENT;ASSIGNOR:SRC COMPUTERS, LLC;REEL/FRAME:031263/0288 Effective date: 20130923 |
|
AS | Assignment |
Owner name: SRC COMPUTERS, LLC, COLORADO Free format text: MERGER;ASSIGNOR:SRC COMPUTERS, INC.;REEL/FRAME:031514/0769 Effective date: 20081224 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: PAT HOLDER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: LTOS); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
AS | Assignment |
Owner name: SRC COMPUTERS, LLC, COLORADO Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:FREEMAN CAPITAL PARTNERS LP;REEL/FRAME:037707/0196 Effective date: 20160205 |
|
AS | Assignment |
Owner name: SRC LABS, LLC, MINNESOTA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SRC COMPUTERS, LLC;REEL/FRAME:037820/0147 Effective date: 20160205 |
|
AS | Assignment |
Owner name: SAINT REGIS MOHAWK TRIBE, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SRC LABS, LLC;REEL/FRAME:043174/0318 Effective date: 20170802 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2553) Year of fee payment: 12 |
|
AS | Assignment |
Owner name: DIRECTSTREAM, LLC, COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SAINT REGIS MOHAWK TRIBE;REEL/FRAME:049251/0855 Effective date: 20190521 |
|
AS | Assignment |
Owner name: FG SRC LLC, TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DIRECTSTREAM LLC;REEL/FRAME:051615/0344 Effective date: 20200122 |
|
AS | Assignment |
Owner name: BARINGS FINANCE LLC, AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:RPX CORPORATION;REEL/FRAME:063503/0742 Effective date: 20230119 |
|
AS | Assignment |
Owner name: RPX CORPORATION, CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN SPECIFIED PATENTS;ASSIGNOR:BARINGS FINANCE LLC, AS COLLATERAL AGENT;REEL/FRAME:063723/0139 Effective date: 20230501 |